| 3 | Approval of the Agenda | |
|---|---|---|
| R3-221500 | RAN3#115-e Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-221501 | RAN3#114bis-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-222388 | Guidelines for RAN3 Electronic Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| 8.1 | New Incoming LSs | |
| R3-221660 | LS on updated Rel-17 NR higher-layers parameter list | RAN1 |
| R3-221664 | Reply LS on security protection of RRCResumeRequest message | RAN2 |
| R3-221669 | LS on feMIMO RRC parameters | RAN2 |
| R3-221673 | LS on NR UDC for CU-CP/UP splitting scenario | RAN2 |
| R3-221999 | Discussion on support of UDC in CPUP separation sceanrio | CATT,ZTE |
| R3-222000 | (CR for 38 460)Support of UDC in E1 | CATT,ZTE |
| R3-222001 | (CR for 38 463)Support of UDC in E1 | CATT,ZTE |
| R3-222002 | [Draft]Reply LS on introduction of NR UDC | CATT, ZTE |
| R3-222133 | UDC for CU-CP/UP splitting scenario | Huawei |
| R3-222134 | UDC for CU-CP/UP splitting scenario | Huawei |
| R3-222135 | UDC for CU-CP/UP splitting scenario | Huawei |
| R3-222136 | [DRAFT] Reply LS on UDC for CU-CP/UP splitting scenario | Huawei |
| R3-222334 | Support of UDC in NR | ZTE, CATT |
| R3-222335 | Discussion on support for NR UDC | ZTE |
| R3-222390 | CB: # 1_NRUDC - Summary of email discussion | CATT - moderator |
| R3-222415 | Reply LS on energy efficiency as guiding principle for new solutions | SA5 |
| R3-222483 | LS on full Registration Request upon AMF re-allocation | SA3 |
| R3-222613 | UDC for CU-CP/UP splitting scenario | Huawei, CATT, ZTE, Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-222614 | Support of NR UDC in E1 | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-222724 | Reply LS on NR UDC for CU-CP/UP splitting scenario | CATT, ZTE |
| 8.2 | LSin received during the meeting | |
| R3-222505 | Response LS on NAS PDU delivery during PDU Session modification procedure | SA2 |
| R3-222659 | LS on updated Rel-17 LTE and NR higher-layers parameter list | RAN1 |
| R3-222661 | Reply LS on NR-U channel information and procedures | RAN1 |
| R3-222662 | Reply LS to RAN3 on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN1 |
| R3-222663 | LS on feMIMO RRC parameters | RAN1 |
| R3-222690 | LS on IAB support of NR satellite access | SA2 |
| R3-222691 | LS on RAN feedback for low latency | SA2 |
| R3-222692 | LS on QoS support with PDU Set granularity | SA2 |
| 8.3.1 | Handling of UE Security Capabilities | |
| R3-221621 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221622 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-221623 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221624 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221625 | UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps] | Ericsson, Qualcomm Incorporated, Huawei |
| R3-221626 | UE Security Capabilities signaling in NG-RAN [UE_Sec_Caps] | Ericsson, Qualcomm Incorporated, Huawei |
| R3-221630 | On UE security capability to address SA3 request [UE_Sec_Caps] | Huawei, Ericsson, Qualcomm Incorporated |
| R3-221736 | Presentation of CRs on Handling of UE Security Capabilities | Qualcomm Incorporated |
| R3-221737 | [DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-222183 | (TP for TS 36.423) X2AP Handling of UE Security Capabilities | ZTE |
| R3-222184 | (TP for TS 38.413) NGAP Handling of UE Security Capabilities | ZTE |
| R3-222185 | (TP for TS 38.423) XnAP Handling of UE Security Capabilities | ZTE |
| R3-222391 | CB: # 2_UESecurity_Capability - Summary of email discussion | Qualcomm - moderator |
| R3-222547 | On UE security capability to address SA3 request [UE_Sec_Caps] | Huawei, Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222608 | UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps] | Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222609 | UE Security Capabilities signaling in NG-RAN [UE_Sec_Caps] | Ericsson, Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222610 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-222701 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222702 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222703 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222704 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| 9.2.1 | Others | |
| R3-221771 | Correction to ASN.1 (Transfer of PSCell Location Reporting control information at X2 mobility) | NEC, ZTE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Vodafone |
| R3-222104 | Discussion on misalignment on M8 and M9 measurement configurations | Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Unicom |
| R3-222105 | Misalignment on M8 and M9 measurement configurations | Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Unicom |
| R3-222106 | Misalignment on M8 and M9 measurement configurations | Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Unicom |
| R3-222321 | Semantic description update for the Name List of MDT M8 and M9 measurement configuration | Samsung, ZTE, CATT, Lenovo, Motorola Mobility, China Telecom, China Unicom, Qualcomm Incorporated |
| R3-222343 | Discussion on semantic description update for the name list of MDT M8 and M9 configuration | ZTE, Samsung, Lenovo, Motorola Mobility, China Unicom, China Telecom, Qualcomm Incorporated |
| R3-222344 | Semantic description update for the Name List of MDT M8 and M9 measurement configuration | ZTE, Samsung, CATT, Lenovo, Motorola Mobility, China Unicom, China Telecom, Qualcomm Incorporated |
| R3-222345 | [draft] LS on configuration updates of MDT M8 and M9 in LTE | ZTE |
| R3-222392 | CB: # 3_LTEM8M9_Alignment - Summary of email discussion | ZTE - moderator |
| R3-222524 | CB: # 3_LTEM8M9_Alignment - Summary of email discussion | ZTE - moderator |
| R3-222557 | Misalignment on M8 and M9 measurement configurations | CMCC |
| R3-222594 | Misalignment on M8 and M9 measurement configurations | Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei, China Unicom, Samsung, ZTE, CATT, Lenovo, Motorola Mobility, China Telecom, China Unicom, Qualcomm Incorporated |
| R3-222615 | Misalignment on M8 and M9 measurement configurations | ZTE, Samsung, CATT, Lenovo, Motorola Mobility, China Unicom, China Telecom, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei |
| R3-222616 | Misalignment on M8 and M9 measurement configurations | Samsung, ZTE, CATT, Lenovo, Motorola Mobility, China Unicom, China Telecom, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, CMCC, Huawei |
| 9.3.1 | Direct Data Forwarding with Mobility Between DC and SA | |
| R3-221749 | SN direct data forwarding in inter-system handover | Qualcomm Incorporated |
| R3-221844 | Direct data forwarding in EN-DC to NR SA handover (CR to 36.413) | Qualcomm Incorporated, CATT, CMCC |
| R3-221845 | Direct data forwarding in EN-DC to NR SA handover (CR to 36.423) | Qualcomm Incorporated, CATT, CMCC |
| R3-221976 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung, China Telecom, ZTE |
| R3-222003 | Discussion on direct data forwarding for mobility between DC and SA | CATT,Qualcomm,CMCC |
| R3-222004 | CR for 38.423 on direct data forwarding for mobility between DC and SA | CATT, Qualcomm, CMCC |
| R3-222271 | CR on data forwarding from MR-DC to SA handover | CMCC, CATT, Qualcomm |
| R3-222272 | CR on data forwarding between EN-DC/MR-DC and SA handover | CMCC, CATT, Qualcomm |
| R3-222295 | direct between DC and SA disc | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222296 | direct between DC and SA S1 CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222297 | direct between DC and SA NG CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222298 | Direct Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
| R3-222299 | Direct Data forwarding address allocation for handover to EN-DC S1 CR | Samsung, Verizon Wireless, ZTE |
| R3-222300 | Direct Data forwarding address allocation for handover to EN-DC X2 CR | Samsung, Verizon Wireless, ZTE |
| R3-222393 | CB: # 4_DirectDataFwd_DCtoSA - Summary of email discussion | Samsung - moderator |
| R3-222487 | direct between DC and SA S1 CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222488 | direct between DC and SA NG CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222489 | Direct Data forwarding address allocation for handover to EN-DC S1 CR | Samsung, Verizon Wireless, ZTE |
| R3-222490 | Direct Data forwarding address allocation for handover to EN-DC X2 CR | Samsung, Verizon Wireless, ZTE |
| R3-222607 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung, China Telecom, ZTE |
| R3-222743 | CR for 38.423 on direct data forwarding for mobility between DC and SA | CATT, Qualcomm, CMCC |
| R3-222745 | direct between DC and SA S1 CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222746 | direct between DC and SA NG CR | Samsung, Huawei, ZTE, Verizon Wireless |
| R3-222819 | CR on data forwarding between EN-DC/MR-DC and SA handover | CMCC, CATT, Qualcomm |
| 9.3.2 | Dynamic ACL | |
| R3-221706 | Discussion on ACL remaining issues | Huawei, Deutsche Telekom, Ericsson, China Telecom |
| R3-221870 | Avoiding delayed HO in deployments supporting dynamic ACL for data forwarding | Nokia, Nokia Shanghai Bell |
| R3-222005 | Discussion on ACL for handover from SA to DC scenario | CATT |
| R3-222006 | CR for 38.423 on ACL for handover from SA to DC scenario | CATT |
| R3-222007 | CR for 36.423 on ACL for handover from SA to DC scenario | CATT |
| R3-222097 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222098 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222099 | Dynamic ACL over X2 CR 38.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222108 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222109 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222110 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222148 | Discussion on ACL issues | ZTE Corporation |
| R3-222149 | Correction for dynamic ACL on mobility from SA to MRDC | ZTE Corporation |
| R3-222150 | Correction for dynamic ACL on mobility from SA to ENDC | ZTE Corporation |
| R3-222175 | Discussion on ACL issues | ZTE Corporation |
| R3-222176 | Correction for dynamic ACL on mobility from SA to MRDC | ZTE Corporation |
| R3-222177 | Correction for dynamic ACL on mobility from SA to ENDC | ZTE Corporation |
| R3-222394 | CB: # 5_DynamicACL - Summary of email discussion | Ericsson - moderator |
| R3-222503 | Reply LS On ACL support for Indirect Data Forwarding | SA2 |
| R3-222762 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom, Ericsson |
| R3-222763 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, Ericsson |
| R3-222783 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-222784 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| 9.3.5.1 | Other Corrections | |
| R3-221702 | [DRAFT] Reply LS on the user consent for trace reporting | Apple [to become RAN3] |
| R3-221703 | On user consent for RLF/CEF | Apple |
| R3-221704 | User consent for location information in RLF/CEF | Apple |
| R3-221705 | User consent for location information in RLF/CEF | Apple |
| R3-221707 | Offered GBR in NR-DC | Nokia, Nokia Shanghai Bell |
| R3-221756 | Clarification of the usage of an IE in case of DAPS HO | Nokia, Nokia Shanghai Bell |
| R3-221757 | Clarification of the usage of an IE in case of DAPS HO | Nokia, Nokia Shanghai Bell |
| R3-221807 | Correction of Intra-System Data Forwarding | Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom |
| R3-221808 | Correction of Intra-System Data Forwarding | Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom |
| R3-221829 | MRO corrections | Huawei |
| R3-221900 | (Stage-2) Clarification on IAB Address Remove | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, CATT, Samsung |
| R3-221901 | (Stage-3) Clarification on IAB Address Remove | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, CATT, Samsung |
| R3-221933 | Correction in NG Setup Response for R16 | RadiSys, Reliance JIO |
| R3-221952 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
| R3-221953 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
| R3-221959 | Correction of SNPN setup failure | Huawei, Deutsche Telekom, Orange, Qualcomm Incorporated |
| R3-221960 | Correction of frequency information for DL only cell for ENDC | Huawei, Deutsche Telekom, China Telecom |
| R3-222008 | Correction on the ASN.1 for neighbour cell information | CATT,Ericsson,Huawei,ZTE,Samsung,Nokia,Nokia Shanghai Bell |
| R3-222054 | On Resuming in NPN-only cells | Ericsson, Verizon Wireless, Qualcomm |
| R3-222055 | Support of NPN-only cells | Ericsson, Verizon Wireless, Qualcomm |
| R3-222090 | Unsuccessful Mobility Setting Change | Ericsson, CATT, NEC, Samsung, Nokia, Nokia Shanghai Bell |
| R3-222103 | Correction for stage 2 description on Immediate MDT configurations for UE in inactive | Ericsson |
| R3-222113 | Accurate retainability measurements for CP/UP separation | Ericsson, BT |
| R3-222114 | Accurate retainability measurements for CP/UP separation - Solution A | Ericsson, BT |
| R3-222137 | Correction of data forwarding for intra-5GS system handover | Huawei |
| R3-222138 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange |
| R3-222139 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell |
| R3-222186 | Clarification for handling of end marker packets_R15 | ZTE |
| R3-222187 | Clarification for handling of end marker packets_R16 | ZTE |
| R3-222236 | Correction on NG interface management messages | Huawei, Deutsche Telekom, Orange |
| R3-222237 | End markers from 5GC during handover | Huawei |
| R3-222288 | Correction of S-NODE MODIFICATION CONFIRM message | Samsung, Verizon Wireless, Huawei, ZTE |
| R3-222289 | Correction of S-NODE MODIFICATION CONFIRM message | Samsung, Verizon Wireless, Huawei, ZTE |
| R3-222306 | Discussion on F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
| R3-222307 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
| R3-222325 | Remaining issues on UP Security Policy Updated | China Telecom, CATT |
| R3-222326 | Security indication in the modification procedure over E1 interface | China Telecom,CATT |
| R3-222327 | Security indication in the modification procedure over E1 interface | China Telecom,CATT |
| R3-222331 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
| R3-222332 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
| R3-222348 | Correction on security policy update via E1AP Bearer Context Modification procedure | Intel Corporation |
| R3-222349 | Correction on Security indication in the modification procedure over Rel-15 E1 interface | Intel Corporation |
| R3-222350 | Correction on Security indication in the modification procedure over Rel-16 E1 interface | Intel Corporation |
| R3-222377 | Accurate retainability measurements for CP/UP separation - Solution B | Ericsson, BT |
| R3-222384 | Mobility Parameters Modification Range | Ericsson-LG Co., LTD |
| R3-222395 | CB: # 6_UserConsent - Summary of email discussion | Apple - moderator |
| R3-222396 | CB: # 7_NPNCorrec - Summary of email discussion | Huawei - moderator |
| R3-222397 | CB: # 8_SecPolicy_E1 - Summary of email discussion | Intel - moderator |
| R3-222398 | CB: # 9_SONMDTCorrec - Summary of email discussion | Ericsson - moderator |
| R3-222457 | Response to R3-222186 and R3-222237 | Nokia, Nokia Shanghai Bell |
| R3-222511 | CB: # 89_IntraSystemDF - Summary of email discussion | Nokia - moderator |
| R3-222512 | Correction of Intra-System Data Forwarding | Nokia, Nokia Shanghai Bell, CATT, Orange, Verizon Wireless, Deutsche Telekom |
| R3-222513 | CB: # 88_F1U_Delay - Summary of email discussion | Samsung - moderator |
| R3-222514 | CB: # 90_EndMarker - Summary of email discussion | ZTE - moderator |
| R3-222515 | Clarification of the usage of an IE in case of DAPS HO | Nokia, Nokia Shanghai Bell |
| R3-222516 | Clarification of the usage of an IE in case of DAPS HO | Nokia, Nokia Shanghai Bell |
| R3-222517 | Correction of frequency information for DL only cell for ENDC | Huawei, Deutsche Telekom, China Telecom |
| R3-222521 | Correction for stage 2 description on Immediate MDT configurations for UE in inactive | Ericsson |
| R3-222526 | CB: # 7_NPNCorrec - Summary of email discussion | Huawei - moderator |
| R3-222538 | CB: # 6_UserConsent - Summary of email discussion | Apple - moderator |
| R3-222635 | Correction of SNPN setup failure | Huawei, Deutsche Telekom, Orange, Qualcomm Incorporated |
| R3-222832 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
| R3-222836 | LS on Handling of end marker packets | ZTE |
| R3-222843 | Security indication in the modification procedure over E1 interface | China Telecom, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT, Intel Corporation |
| R3-222844 | Security indication in the modification procedure over E1 interface | Nokia, Nokia Shanghai Bell, China Telecom, Huawei, ZTE, CATT, Intel Corporation |
| 10.1 | General | |
| R3-221504 | BLCR to 36.423:Support of MDT enhancement | CATT |
| R3-221505 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| R3-221511 | (BLCR to 37.340) Addition of SON features enhancement | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-221512 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-221519 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-221520 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-221544 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-221545 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-221546 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-221547 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-221548 | BLCR to 37.320: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-221549 | BLCR to 38.413: Support of MDT enhancement | Huawei |
| R3-221550 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-221567 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| R3-221568 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm Inc. |
| R3-221588 | BLCR to 38.413: Support of MDT enhancement | Ericsson |
| R3-221827 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm Incorporated |
| R3-222267 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-222417 | CB: # SONMDT1_Workplan_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-222495 | BLCR to 38.413: Support of MDT enhancement | Huawei |
| R3-222497 | BLCR to 38.423: Support of MDT enhancement | Huawei |
| R3-222632 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-222633 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-222634 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm Inc. |
| R3-222910 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
| R3-222911 | BLCR to 36.423_Addition of SON features enhancement | CATT, CMCC, Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222912 | (BLCR to 37.340) Addition of SON features enhancement | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, CMCC |
| R3-222913 | BLCR to 38.300_Addition of SON features enhancement | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, ZTE, CATT, Lenovo |
| R3-222914 | BLCR to 38.413_Addition of SON features enhancement | Ericsson, CATT, Nokia, Nokia Shanghai Bell |
| R3-222915 | BLCR to 38.423_Addition of SON features enhancement | Samsung, CMCC, CATT, Ericsson |
| R3-222916 | BLCR to 38.473_Addition of SON features enhancement | Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-222917 | BLCR to 38.413: Support of MDT enhancement | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222918 | BLCR to 38.423: Support of MDT enhancement | Huawei, Nokia, Nokia Shanghai bell, CMCC, Ericsson |
| R3-222976 | BLCR to 38.401_Addition of SON features enhancement | ZTE, Nokia, Nokia Shanghai Bell, CMCC |
| R3-222977 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm Inc., Ericsson |
| R3-222980 | BLCR to 38.473: Support of MDT enhancement | Samsung, Nokia, Nokia Shanghai Bell |
| 10.2.1.3 | Successful Handover Report | |
| R3-222014 | (TP on SON for 38.300) Successful Handover Report | CATT |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-221712 | Consideration on UE history information | China Telecommunication |
| R3-221830 | (TP for SON BLCR for 38.423, 38.413, 36.413 and 36.423) UE History Information in MR-D | Huawei |
| R3-222011 | Enhancement of UE history information in MR-DC scenario | CATT,CMCC |
| R3-222012 | (TP on SON for 36.413) Addition of UE history information for SN | CATT,CMCC |
| R3-222013 | (TP on SON for 36.423) Addition of UE history information for SN | CATT,CMCC |
| R3-222067 | (TP for SON BL CR for TS 38.423, TS 38.413, TS 36.413) UE History Information for Secondary Node | Ericsson |
| R3-222268 | (TP to SON BLCR TS 38.413)UE history information in MR-DC_final | CMCC, CATT |
| R3-222269 | (TP to SON BLCR TS 38.423)UE history information in MR-DC_final | CMCC, CATT |
| R3-222378 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222379 | (TP for SON BL CR for TS 37.340) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222380 | (TP for SON BL CR for TS 38.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222381 | (TP for SON BL CR for TS 36.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222382 | (TP for SON BL CR for TS 38.413) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222383 | (TP for SON BL CR for TS 36.413) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222387 | UE History Information in MR-DC | Samsung R&D Institute UK |
| R3-222418 | CB: # SONMDT2_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-222638 | CB: # SONMDT2_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-222725 | (TP on SON for 36.423) Addition of UE history information for SN | CATT,CMCC |
| R3-222760 | (TP for SON BLCR for 36.413) UE History Information in MR-DC | Huawei |
| R3-222817 | (TP for SON BL CR for TS 38.423) UE History Information for Secondary Node | Ericsson |
| R3-222820 | (TP for SON BL CR for TS 37.340) Introduce UHI in MR-DC | CMCC, ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-222837 | (TP for SON BL CR for TS 38.413) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-221777 | Per-Slice Mobility Settings Change | NEC |
| R3-221831 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei |
| R3-221913 | (TP for 36.423) Support of PSCell MLB | CATT |
| R3-221935 | [TP to SON BL CR for TS 38.423] Per-beam mobility setting change | Nokia, Nokia Shanghai Bell |
| R3-221936 | [TP to SON BL CR for TS 38.473] Per-beam mobility setting change | Nokia, Nokia Shanghai Bell |
| R3-222066 | Further Discussion on Load Balancing Enhancements in NR | ZTE, China Telecom |
| R3-222068 | (TP for SON BL CR for TS 38.423, TS 36.423) MLB enhancements | Ericsson |
| R3-222258 | (TP for SON BLCR to 38.473) PRB usage for MIMO | CMCC |
| R3-222259 | (TP for SON BLCR to 36.423) PRB usage for MIMO | CMCC |
| R3-222419 | CB: # SONMDT3_LoadBalance - Summary of email discussion | Nokia - moderator |
| R3-222508 | (TP for SON BL CR for TS 38.423, TS 36.423) MLB enhancements | Ericsson |
| R3-222622 | (TP for 36.423) Support of PSCell MLB | CATT |
| R3-222639 | CB: # SONMDT3_LoadBalance - Summary of email discussion | Nokia - moderator |
| R3-222873 | (TP for SON BL CR for TS 38.423) UE History Information for Secondary Node | Ericsson |
| R3-222878 | (TP for 36.423) Support of PSCell MLB | CATT |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-221713 | MRO for SN Change Failure | China Telecommunication |
| R3-221765 | [TP to SON BL CRs to 38.423, NR_ENDC_SON_MDT_enh] MRO for PSCell change failure | Nokia, Nokia Shanghai Bell |
| R3-221766 | [TP to SON BL CRs to 36.423, NR_ENDC_SON_MDT_enh] MRO for PSCell change failure | Nokia, Nokia Shanghai Bell |
| R3-221832 | (TP for SON BLCR for 38.423, 38.300) MRO for SN Change Failure | Huawei |
| R3-222010 | (TP on SON for 38.423)Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-222069 | (TP for SON BL CR for TS 38.300, TS 38.423) MRO for SN change failure | Ericsson |
| R3-222304 | MRO for SN Change Failure | Samsung |
| R3-222305 | TP for SON BLCR for TS 38.423: Support of SON for SN change failure | Samsung |
| R3-222364 | Further consideration on MRO SN change failure | ZTE |
| R3-222420 | CB: # SONMDT4_SNChangeFailure - Summary of email discussion | Samsung - moderator |
| R3-222640 | CB: # SONMDT4_SNChangeFailure - Summary of email discussion | Samsung - moderator |
| R3-222750 | TP for SON BLCR for TS 38.423: Support of SON for SN change failure | Samsung |
| R3-222761 | (TP for SON BLCR for 38.300) MRO for SN Change Failure | Huawei |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-222015 | (TP on SON for 38.473) On naming issue for PRACH coordination | CATT |
| R3-222016 | (TP on SON for 36.300) Description for RACH optimisation in EN-DC | CATT |
| R3-222070 | (TP for SON BL CR for TS 38.473) RACH conflict resolution | Ericsson |
| R3-222119 | (TP for SON BL CR for TS 38.473) Addressing a few remaining aspects in RACH Optimization | Nokia, Nokia Shanghai Bell |
| R3-222421 | CB: # SONMDT5_RACHOpt - Summary of email discussion | CATT - moderator |
| R3-222641 | CB: # SONMDT5_RACHOpt - Summary of email discussion | CATT - moderator |
| R3-222726 | (TP on SON for 38.473) On naming issue for PRACH coordination | CATT |
| R3-222869 | (TP on SON for 38.473) On naming issue for PRACH coordination | CATT |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-221778 | Cell Edge Capacity Issue | NEC |
| R3-221833 | (TP for SON BLCR for 38.473, 38.401,38.300, 38.470, 38.423) Coverage and Capacity Optimization | Huawei |
| R3-221866 | (TP for SON BL CR for TS 38.300) Remaining open points on CCO | Nokia, Nokia Shanghai Bell |
| R3-221867 | (TP for SON BL CR for TS 38.401) Support of CCO in split architecture | Nokia, Nokia Shanghai Bell |
| R3-222071 | (TP for SON BL CR for TS 38.300, TS 38.401, TS 38.473) NR CCO solution | Ericsson |
| R3-222077 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE, China Telecom |
| R3-222088 | (TP for SON BL CR 38.300) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-222089 | (TP for SON BL CR 38.423 and 38.473) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-222303 | TP for SON BLCR for TS 38.300: Support of SON for CCO | Samsung |
| R3-222422 | CB: # SONMDT6_CCO - Summary of email discussion | Ericsson - moderator |
| R3-222643 | CB: # SONMDT6_CCO - Summary of email discussion | Ericsson - moderator |
| R3-222729 | (TP for SON BLCR for 38.300) Coverage and Capacity Optimization | Huawei |
| R3-222752 | (TP for SON BLCR for 38.401) Coverage and Capacity Optimization | Samsung |
| R3-222756 | (TP for SON BL CR 38.423) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-222811 | (TP for SON BL CR for TS 38.473) NR CCO solution | Ericsson |
| 10.2.4 | Inter-System Load Balancing | |
| R3-222072 | (TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing | Ericsson |
| R3-222260 | (TP for SON BLCR to 38.413) Leftover issues for inter-system load balancing | CMCC |
| R3-222361 | (TP for SON BL CR 36.300) Inter-system Load Balancing | ZTE,China Telecom, China Unicom |
| R3-222362 | (TP for SON BL CR 38.300) Inter-system Load Balancing | ZTE,China Telecom, China Unicom |
| R3-222363 | (TP for SON BL CR 38.413) Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-222423 | CB: # SONMDT7_InterSystemLB - Summary of email discussion | CMCC - moderator |
| R3-222647 | CB: # SONMDT7_InterSystemLB - Summary of email discussion | CMCC - moderator |
| R3-222648 | (TP for SON BL CR 38.413) Inter-system Load Balancing | ZTE, China Telecom, China Unicom |
| R3-222765 | (TP for SON for TS 38.300) Inter-System Load Balancing | Ericsson |
| R3-222766 | (TP for SON for TS 36.300) Inter-System Load Balancing | Ericsson |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-221834 | (TP for SON BLCR for 38.423) Mobility enhancements | Huawei |
| R3-221977 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-222009 | (TP on SON for 38.423) Discussion on MRO for mobility Enhancement | CATT |
| R3-222073 | MRO for CHO and DAPS | Ericsson |
| R3-222301 | TP for TS 38.300: SON enhancements for CHO | Samsung, Verizon Wireless |
| R3-222302 | TP for SON BLCR for 38.423: Support of CHO for MRO | Samsung, Verizon Wireless |
| R3-222424 | CB: # SONMDT8_MobilityEnh - Summary of email discussion | Lenovo - moderator |
| R3-222621 | TP for TS 38.300: SON enhancements for CHO | Samsung, Verizon Wireless |
| R3-222792 | CB: # SONMDT8_MobilityEnh - Summary of email discussion | Lenovo - moderator |
| R3-222879 | TP for SON BLCR for 38.423: Support of CHO for MRO | Samsung, Verizon Wireless |
| 10.3.2.1 | MDT Enhancements | |
| R3-221720 | (TP for MDT BL CR for TS38.413, TS38.423): Valid RAT MDT configuration | Huawei |
| R3-221961 | Discussion on the propagation of immediate MDT configuration in Xn HO | CATT |
| R3-222188 | Leftover issue on MDT | ZTE |
| R3-222189 | (TP for MDT BL CR for TS38.413)Introduce PDCP Excess Packet Delay | ZTE |
| R3-222190 | [Draft]LS on introduce PDCP Excess Packet Delay | ZTE |
| R3-222371 | (TP for MDT BL CR for TS 38.413) MDT User consent updates | Ericsson, Deutsche Telekom |
| R3-222374 | (TP for MDT BL CR 38.423) On Valid RAT MDT in Xn | CATT |
| R3-222425 | CB: # SONMDT9_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-222553 | Reply LS On User Consent Updating | CT4 |
| R3-222666 | CB: # SONMDT9_MDTEnh - Summary of email discussion | ZTE - moderator |
| R3-222744 | (TP for MDT BL CR for TS38.423): Valid RAT MDT configuration | Huawei, Nokia, Nokia Shanghai Bell |
| R3-222833 | (TP for MDT BL CR for TS38.413)Introduce PDCP Excess Packet Delay | ZTE |
| R3-222870 | Reply LS on User Consent Updating | SA3 |
| R3-222883 | (TP for MDT BL CR for TS38.413)Introduce PDCP Excess Packet Delay | ZTE, Ericsson |
| 10.3.2.2 | MDT for MR-DC | |
| R3-221721 | (TP for MDT BL CR for TS38.413): S-based MDT for NR-DC | Huawei |
| R3-221868 | Activation of signalling-based immediate MDT in MN/SN | Nokia, Nokia Shanghai Bell |
| R3-222426 | CB: # SONMDT10_MRDC - Summary of email discussion | Huawei - moderator |
| 10.4 | Support for L2 Measurements | |
| R3-221722 | Discussion on MDT M6 calculation for split bearers in MR-DC | Huawei |
| R3-221723 | [DRAFT] Reply LS on MDT M6 calculation for split bearers in MR-DC | Huawei |
| R3-221869 | Solution down-selection for M6 measurement for split bearer | Nokia, Nokia Shanghai Bell |
| R3-222074 | Continuation of the discussion on L2 (M6) Measurements | Ericsson |
| R3-222191 | Leftover issue for L2 measurement | ZTE |
| R3-222192 | (TP for MDT BL CR for TS37.320)M6 calculation for split bearer in MR-DC | ZTE |
| R3-222427 | CB: # SONMDT11_L2Measurements - Summary of email discussion | Ericsson - moderator |
| R3-222814 | CB: # SONMDT11_L2Measurements - Summary of email discussion | Ericsson - moderator |
| R3-222815 | Reply LS on MDT M6 calculation for split bearers in MR-DC | Ericsson |
| R3-222868 | Reply LS on MDT M6 calculation for split bearers in MR-DC | Ericsson |
| 10.5 | SON/MDT Optimizations for NR-U | |
| R3-221665 | Reply LS on NR-U channel information and procedures | RAN2 |
| R3-221724 | MRO Optimizations for NR-U | Huawei |
| R3-221767 | Completion of the work on SON for NR-U | Nokia, Nokia Shanghai Bell |
| R3-221978 | SON Enhancements for NR-U | Lenovo, Motorola Mobility |
| R3-222053 | (TP for SON BL CR 38.423 and 38.473) Load Balancing Optimization for NR-U | ZTE |
| R3-222075 | (TP for SON BL CR for TS 38.423, TS 38.473): Progress on MLB for NR-U | Ericsson |
| R3-222357 | Support of SON for NR-U | Samsung |
| R3-222358 | TP for SON BLCR for TS 38.423: Support of SON for NR-U | Samsung |
| R3-222428 | CB: # SONMDT12_NRU - Summary of email discussion | Nokia - moderator |
| R3-222498 | (TP for SON BL CR for TS 38.423, TS 38.473): Progress on MLB for NR-U | Ericsson |
| R3-222824 | TP for SON BLCR for TS 38.423: Support of SON for NR-U | Samsung |
| R3-222835 | (TP for SON BL CR for TS 38.473): Progress on MLB for NR-U | Ericsson |
| R3-222880 | CB: # SONMDT12_NRU - Summary of email discussion | Nokia - moderator |
| R3-222884 | (TP for SON BL CR for TS 38.473): Progress on MLB for NR-U | Ericsson, Samsung |
| R3-222885 | TP for SON BLCR for TS 38.423: Support of SON for NR-U | Samsung, Ericsson |
| 11.1 | General | |
| R3-221529 | Support for Redcap Ues | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, Qualcomm Incorporated, CATT |
| R3-221530 | Support for Redcap Ues | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO |
| R3-221531 | Draft BL CR to TS 38.300 on RedCap UEs impacts to NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, CATT, Qualcomm Inc., ZTE, Radisys, Reliance JIO |
| R3-221532 | BL CR to 38.401 Support for Redcap Ues | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Radisys |
| R3-221533 | BL CR to 38.470 Support for Redcap Ues | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT, Qualcomm Incorporated, Radisys, Reliance JIO |
| R3-221571 | CR to TS38.473 for RedCap support | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, CATT, Radisys, Reliance JIO |
| R3-222407 | CB: # RedCap1_BLCRs - Summary of email discussion | ZTE - moderator |
| R3-222528 | Support for Redcap Ues | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, Qualcomm Incorporated, CATT, Radisys, Reliance JIO |
| R3-222529 | Support for Redcap Ues | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO |
| R3-222530 | BL CR to 38.470 Support for Redcap Ues | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT, Qualcomm Incorporated, Radisys, Reliance JIO |
| R3-222531 | CR to TS38.473 for RedCap support | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, CATT |
| R3-222945 | Draft BL CR to TS 38.300 on RedCap UEs impacts to NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, CATT, Qualcomm Inc., ZTE, Radisys, Reliance JIO |
| R3-222946 | BL CR to 38.401 Support for Redcap Ues | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Radisys |
| R3-222947 | Support for Redcap Ues | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Samsung, Qualcomm Incorporated, CATT, Radisys, Reliance JIO, Huawei |
| R3-222948 | Support for Redcap Ues | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO, Huawei |
| R3-222949 | BL CR to 38.470 Support for Redcap Ues | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT, Qualcomm Incorporated, Radisys, Reliance JIO |
| R3-222950 | CR to TS38.473 for RedCap support | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, CATT, Radisys, Reliance JIO, Huawei |
| 11.2 | Support for RedCap Capability Exchange | |
| R3-221772 | (TP for XnAP BL CR on RedCap) RedCap Mobility Handling and Cause Value | NEC |
| R3-221773 | (TP for NGAP BL CR on RedCap) RedCap Mobility Handling and Cause Value | NEC |
| R3-221809 | (TP for TS 38.413) Coordination of Redcap Capabilities across gNBs with no Xn | Nokia, Nokia Shanghai Bell |
| R3-221914 | (TP for TS38.423 and TS38.413) Support of RedCap UE mobility | CATT |
| R3-221918 | RedCap leftover issues | Huawei |
| R3-221932 | (TP for TS 38.413 on RedCap UE Support) Cause values for Xn and NG mobility failure for RedCap UEs | RadiSys, Reliance JIO |
| R3-222408 | CB: # RedCap2_UECapability - Summary of email discussion | NEC - moderator |
| R3-222532 | RedCap leftover issues | Huawei |
| R3-222533 | CB: # RedCap2_UECapability - Summary of email discussion | NEC - moderator |
| R3-222735 | (TP for TS 38.413 on RedCap UE Support) Cause values for Xn and NG mobility failure for RedCap UEs | RadiSys, Reliance JIO, ZTE, NEC |
| 11.3 | Support for the Extended DRX enhancements for RedCap UEs | |
| R3-221744 | (TP for XnAP BL CR on RedCap) Proposed updates to the XnAP BL CR | Qualcomm Incorporated, Huawei, Ericsson |
| R3-221803 | (TP for NGAP BL CR on RedCap) Proposed updates to the NGAP BL CR | Ericsson, Qualcomm Inc., Huawei |
| R3-221805 | TP to RedCap TS 38.300 BL CR: Addition of Inactive eDRX | Ericsson, Qualcomm Inc. |
| R3-221810 | (TP for TS 38.473 and 38.470) Support of eDRX for Redcap UEs | Nokia, Nokia Shanghai Bell |
| R3-221919 | Supporting Redcap UEs over F1 interface | Huawei, Qualcomm Incorporated, Ericsson |
| R3-221920 | (TP to BL CR 38.470) Paging for RedCap UEs | Huawei |
| R3-222256 | (TP for TS 38.473) Extended DRX Enhancement for RedCap Ues | CMCC |
| R3-222317 | (TP to BL CR of TS38.473) Discussion on the remaining issues of Rel-17 RedCap | Samsung |
| R3-222359 | (TP for RedCap BL CR 38.470) RedCap Paging | ZTE |
| R3-222360 | (TP for RedCap BL CR 38.473) RedCap Paging | ZTE |
| R3-222409 | CB: # RedCap3_eDRX - Summary of email discussion | Ericsson - moderator |
| R3-222486 | (TP for RedCap BL CR 38.470) RedCap Paging | ZTE, Ericsson |
| R3-222534 | CB: # RedCap3_eDRX - Summary of email discussion | Ericsson - moderator |
| R3-222709 | Supporting Redcap UEs over F1 interface | Huawei, Qualcomm Incorporated, Ericsson |
| 12.2 | Support for Carrier Selection and Carrier Specific Configuration | |
| R3-221811 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-221939 | (TP to TS36.413 and TS38.413) Support CEL based paging carrier selection | ZTE |
| R3-222156 | (TPs to TS 36.413, 38.413) CE based Carrier Selection for NB-IoT | Huawei |
| R3-222459 | CB: # NBIoTMTC1_CarrierSelect - Summary of email discussion | Huawei - moderator |
| R3-222642 | Reply LS to RAN3 on coverage-based carrier selection | RAN2 |
| 13.1 | General | |
| R3-221510 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-221513 | CP-based Congestion Mitigation for IAB Network | ZTE |
| R3-221551 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-221569 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-221591 | draft CR for 38.300 on Rel-17 IAB enhancements | Qualcomm Incorporated |
| R3-221595 | BL CR to TS 38.401 on support of eIAB | Huawei |
| R3-221840 | Updated Workplan for Rel-17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| R3-222125 | (TP for NR QoE for BL CR 38.401) Rapporteur corrections and clean-ups | Huawei |
| R3-222460 | CB: # 1301_IAB_BL_CRs - Summary of email discussion | Qualcomm - moderator |
| R3-222509 | (TP for NR_IAB_enh for BL CR 38.401) Rapporteur corrections and clean-ups | Huawei |
| R3-222919 | BL CR to TS 38.401 on support of eIAB | Huawei, Nokia, Nokia Shanghai Bell |
| R3-222920 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-222921 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-222922 | CP-based Congestion Mitigation for IAB Network | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-222923 | CP-based Congestion Indication for IAB Networks | Ericsson |
| 13.2.1.1 | Procedure Details | |
| R3-221681 | (TP for IAB BL CR for TS 38.401) IAB Inter-Donor Topology Adaptation | Ericsson, Verizon |
| R3-221689 | (TP for IAB BL CR for TS 38.401) Procedures for IAB inter-donor migration, topology redundancy and RLF recovery | ZTE |
| R3-221768 | (TP for IAB BL CR for TS 38.420) Discussion on IAB-specific procedures in TS 38.420 | ZTE |
| R3-221841 | (TP for IAB BL CR for TS 38.401) IAB Inter-Donor Procedures St2 | Qualcomm Incorporated |
| R3-221888 | (TP to BL CR of TS38.401) Discussion on inter-donor partial migration and RLF recovery | Fujitsu |
| R3-221889 | (TP to BL CR of TS38.401) Disussion on topology reduncancy procedure | Fujitsu |
| R3-222141 | (TP for TS38.401 BL CR) discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-222142 | (TP for TS38.423 BL CR) discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-222312 | (TP to BL CR of TS38.401) Discussion on inter-donor IAB node partial migration | Samsung |
| R3-222461 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Qualcomm - moderator |
| R3-222715 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Qualcomm - moderator |
| R3-222740 | (TP for IAB BL CR to TS 38.401): IAB Inter-CU topology adaptation procedures | Qualcomm (Moderator) |
| R3-222748 | (TP for TS38.423 BL CR) discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-222851 | (TP for IAB BL CR for TS 38.420) Discussion on IAB-specific procedures in TS 38.420 | ZTE |
| R3-222855 | (TP for TS38.423 BL CR) discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| 13.2.2 | Reduction of Service Interruption | |
| R3-221682 | (TP for IAB BL CR for TS 38.401) The Reuse of Inter-Donor Tunnelling for Avoidance of Descendant Node Reconfiguration | Ericsson |
| R3-221690 | (TP for IAB BL CR for TS 38.473) Discussion on service interruption reduction | ZTE |
| R3-221890 | Avoidance of descendant node reconfiguration | Fujitsu |
| R3-221979 | Discussion on avoidance of descendant node reconfiguration | Lenovo, Motorola Mobility |
| R3-222127 | (TP for BL CR for TS 38.401) Further discussion on reduction of service interruption | Huawei |
| R3-222462 | CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion | Fujitsu - moderator |
| R3-222842 | CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion | Fujitsu - moderator |
| 13.2.3 | Topology Redundancy | |
| R3-221683 | (TP for IAB BL CR for TS 38.423) IAB Inter-Donor Topology Redundancy | Ericsson |
| R3-221691 | Discussion on Inter-topology transport | ZTE |
| R3-221842 | IAB Inter-Donor Procedures St3 | Qualcomm Incorporated |
| R3-221980 | Remaining issues for IAB inter-donor topology adaptation | Lenovo, Motorola Mobility |
| R3-222126 | (TP for BL CR for TS 38.423) Further discussion on Inter-Donor IAB Node Migration | Huawei |
| R3-222128 | (TP for BL CR for TS 38.423) Further discussion on inter-CU topology redundancy | Huawei |
| R3-222131 | (TP for BL CR for TS 38.473) F1AP enhancement to enable inter-topology (re)routing | Huawei |
| R3-222143 | (TP for TS38.423 BL CR) discussion on Inter-Donor IAB Topology Redundancy | Nokia, Nokia Shanghai Bell |
| R3-222313 | (TP to BL CR of TS38.423) Discussion on XnAP stage-3 issues for Rel-17 eIAB | Samsung |
| R3-222314 | (TP to BL CR of TS38.473) Discussion on F1AP stage-3 issues for Rel-17 eIAB | Samsung |
| R3-222463 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Huawei - moderator |
| R3-222500 | (TP for IAB BL CR for TS 38.423) IAB Inter-Donor Topology Redundancy | Ericsson |
| R3-222673 | (TP for BL CR for TS 38.423) Further discussion on inter-CU topology redundancy | Huawei, Samsung, ZTE |
| R3-222675 | (TP for BL CR for TS 38.473) F1AP enhancement to enable inter-topology (re)routing | Huawei, Samsung |
| R3-222685 | (TP for IAB BL CR for TS 38.470) Header Rewriting Configuration in IAB | ZTE |
| R3-222717 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Huawei - moderator |
| R3-222845 | (TP for NR_IAB_enh BL CR for TS 38.401) CB #1304_IAB_Top_Red | Huawei |
| R3-222857 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Huawei - moderator |
| R3-222882 | (TP for BL CR for TS 38.423) Further discussion on inter-CU topology redundancy | Huawei, Samsung, ZTE |
| 13.3.1 | Congestion Mitigation | |
| R3-221684 | (TP for IAB BL CR for TS 38.473) Congestion Mitigation in IAB Networks | Ericsson |
| R3-222129 | (TP for BL CR for TS 38.473) Further discussion on congestion mitigation | Huawei |
| R3-222464 | CB: # 1305_IAB_Con_Mit - Summary of email discussion | Ericsson - moderator |
| R3-222502 | TP for the IAB BL CR for TS 38.473 | Ericsson |
| R3-222758 | TP for the IAB BL CR for TS 38.473 | Ericsson, Huawei, Samsung |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-221685 | (TP for IAB BL CR for TS 38.473) Inter-Donor-DU Tunnelling | Ericsson |
| R3-221692 | Discussion on inter-donor-DU re-routing in IAB | ZTE |
| R3-221891 | Discussion on inter-donor-DU re-routing | Fujitsu |
| R3-221981 | Remaining issues for inter-donor-DU rerouting | Lenovo, Motorola Mobility |
| R3-222130 | (TP for BL CR for TS 38.473/38.423/38.401)Inter-donor re-routing for IAB during topology update | Huawei |
| R3-222144 | (TP for TS38.473 BL CR) discussion on Inter-Donor-DU tunnel | Nokia, Nokia Shanghai Bell |
| R3-222145 | (TP for TS38.423 BL CR) on Inter-Donor-DU tunnel | Nokia, Nokia Shanghai Bell |
| R3-222315 | (TP to BL CR of TS38.473) Discussion on the inter-donor-DU rerouting | Samsung |
| R3-222465 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | Nokia - moderator |
| R3-222674 | (TP for BL CR for TS 38.401) Inter-donor re-routing for IAB during topology update | Huawei, Samsung |
| R3-222686 | (TP to BL CR of TS38.473) Discussion on the inter-donor-DU rerouting | Samsung |
| R3-222741 | (TP for IAB BL CR for TS 38.470) Inter donor-DU re-routing | ZTE |
| R3-222749 | (TP for TS38.423 BL CR) on Inter-Donor-DU tunnel | Nokia, Nokia Shanghai Bell |
| R3-222826 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | Nokia - moderator |
| 13.4.1 | Resource Multiplexing of Child and Parent Links and CLI Management | |
| R3-221686 | (TP for IAB BL CR for TS 38.423) Inter-Donor Resource Coordination in IAB Networks | Ericsson |
| R3-221687 | (TP for IAB BL CR for TS 38.473) Inter-Donor Resource Coordination in IAB Networks | Ericsson |
| R3-221693 | (TP for IAB BL CR for TS 38.473) Resource multiplexing in IAB | ZTE |
| R3-221769 | (TP for IAB BL CR for TS 38.423) Resource multiplexing in IAB | ZTE |
| R3-221843 | (TPs for IAB BL CRs to TS38.423 and TS38.473) IAB multiplexing enhancements and PHY layer configurations | Qualcomm Incorporated |
| R3-222132 | (TP for NR_IAB_enh BL CR for TS 38.473 and TS 38.423) IAB resource multiplexing | Huawei |
| R3-222146 | (TP for TS38.473 BL CR) Resource multiplexing – F1AP enhancements | Nokia, Nokia Shanghai Bell |
| R3-222147 | (TP for TS38.423 BL CR) Resource multiplexing – XnAP enhancements | Nokia, Nokia Shanghai Bell |
| R3-222466 | CB: # 1307_IAB_Res_Multiplex - Summary of email discussion | ZTE - moderator |
| R3-222695 | (TP for IAB BL CR for TS 38.473) Resource multiplexing in IAB | ZTE |
| R3-222696 | (TP for IAB BL CR for TS 38.423) Resource multiplexing in IAB | ZTE |
| R3-222697 | TP to IAB BL CR on 38.420 | ZTE |
| R3-222698 | TP to IAB BL CR on 38.470 | ZTE |
| R3-222799 | LS on upper layers parameters for Rel-17 eIAB | RAN1 |
| R3-222859 | (TP for IAB BL CR for TS 38.473) Resource multiplexing in IAB | ZTE |
| R3-222860 | (TP for IAB BL CR for TS 38.423) Resource multiplexing in IAB | ZTE |
| 14.1 | General | |
| R3-221515 | CPAC BL CR to TS38.401 | ZTE |
| R3-221516 | CPAC BL CR to TS38.463 | Qualcomm |
| R3-221517 | BLCR to TS 38.473 for Conditional PScell Change/Addition | CATT |
| R3-221534 | CPAC BL CR to TS 38.420 | Lenovo, Motorola Mobility |
| R3-221537 | SCG BL CR to TS 37.340 | ZTE |
| R3-221538 | SCG BL CR to TS 38.423 | Ericsson |
| R3-221539 | CPAC BL CR to TS 36.420 | China Telecommunications |
| R3-221540 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-221541 | CPAC BL CR to TS 37.340 | Huawei |
| R3-221572 | SCG BL CR to TS 38.473 | Samsung |
| R3-221579 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-221580 | SCG BL CR to TS 38.401 | Huawei |
| R3-221581 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-221648 | SCG BL CR to TS 38.463 | Lenovo, Motorola Mobility |
| R3-222429 | CB: # MRDC1_BLCRs - Summary of email discussion | Huawei - moderator |
| R3-222543 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-222544 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-222545 | SCG BL CR to TS 38.401 | Huawei |
| R3-222550 | CPAC BL CR to TS 36.420 | China Telecom |
| R3-222551 | SCG BL CR to TS 38.423 | Ericsson |
| R3-222552 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-222559 | SCG BL CR to TS 38.473 | Samsung |
| R3-222903 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-222904 | SCG BL CR to TS 38.401 | Huawei, ZTE |
| R3-222905 | SCG BL CR to TS 38.423 | Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222906 | SCG BL CR to TS 38.463 | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-222907 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, NEC |
| R3-222908 | CPAC BL CR to TS 37.340 | Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222909 | CPAC BL CR to TS 38.423 | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, NEC |
| R3-222975 | SCG BL CR to TS 38.473 | Samsung, Nokia, Nokia Shanghai Bell, ZTE |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-221762 | (TP to SCG BL CR to 38.463, LTE_NR_DC_enh2-Core) Enabling information on SCG use | Nokia, Nokia Shanghai Bell |
| R3-221849 | (TP for SCG BL CR to TS 38.401) Completion of SCG (de)activation | Ericsson |
| R3-221982 | (TP to SCG BLCR to TS38.463) Left E1 F1 issues for SCG (de)activation | Lenovo, Motorola Mobility |
| R3-221983 | (TP to SCG BLCR to TS38.401) CU-CP CU-UP DU coordination for SCG (de)activation | Lenovo, Motorola Mobility |
| R3-222157 | (TP to SCG BL CR for TS 38.401) the SCG status notification to CU-UP | Huawei |
| R3-222202 | Discussion on efficient Activation/Deactivation for SCG | CATT |
| R3-222203 | (TP for SCG BLCR for TS 38463)efficient Activation/Deactivation for SCG | CATT |
| R3-222293 | (TP to SCG BL CR of TS38.463) Discussion on open issues for SCG (de)activation | Samsung |
| R3-222294 | (TP to SCG BL CR of TS38.401) Discussion on open issues for SCG (de)activation | Samsung |
| R3-222338 | TP for SCG BL CR to TS 38.401 | ZTE |
| R3-222339 | TP for SCG BL CR to TS 38.423 36.423 | ZTE |
| R3-222340 | (TP for SCG BL CR to TS 38.473) Assisting information from F1 for SCG (de)activation | ZTE, Samsung, China Telecom |
| R3-222430 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-222554 | TP for SCG BL CR to TS 38.423 | ZTE |
| R3-222555 | TP for SCG BL CR to TS 36.423 | ZTE |
| R3-222556 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-222623 | (TP to SCG BL CR of TS38.473) Discussion on open issues for SCG (de)activation | Samsung |
| R3-222753 | (TP to SCG BLCR to TS38.463) Left E1 F1 issues for SCG (de)activation | Lenovo, Motorola Mobility |
| R3-222806 | (TP to SCG BL CR for TS 38.401) the SCG status notification to CU-UP | Huawei, CATT |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-221661 | LS to RAN3 on CPAC | RAN2 |
| R3-221714 | Remaining issues on CAPC procedures | China Telecommunication |
| R3-221715 | (TP for CPAC BL CR to TS 37.340) Update of MN or SN initiated inter-SN CPC | China Telecommunication |
| R3-221750 | (TP for CPAC BL CR to TS 37.340) Discussion of some outstanding CPAC issues | Qualcomm Incorporated |
| R3-221763 | (TP to CPAC BL CR to 38.423, LTE_NR_DC_enh2-Core) Further development of the CPAC | Nokia, Nokia Shanghai Bell |
| R3-221764 | (TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Further development of the CPAC | Nokia, Nokia Shanghai Bell |
| R3-221774 | RAN3 signalling aspect for the SN Initiated Inter-SN CPC | NEC |
| R3-221788 | (TP for CPAC BLCR to TS36.423) CPAC replace | ZTE |
| R3-221789 | (TP for CPAC BLCR to TS38.423) CPAC replace | ZTE |
| R3-221850 | (TP for CPAC BL CR to TS 37.340) Resolving remaining issues for CPAC | Ericsson, ZTE |
| R3-221851 | (TP for CPAC BL CR to TS 38.423) Resolving the remaining issues for CPAC | Ericsson, Lenovo, Motorola Mobility |
| R3-221852 | [DRAFT] Reply LS on SN initiated inter-SN CPC | Ericsson |
| R3-221950 | Remaining issues on SN initiated conditional PSCell change | NTT DOCOMO INC. |
| R3-221984 | Discussion on CPAC remaining issues | Lenovo, Motorola Mobility |
| R3-222028 | (TPs to CPAC BLCR for TS36.423 and TS38.423) Timer handling in MN initiated SN modification procedure | Google Inc. |
| R3-222029 | (TP to CPAC BLCR to 37.340) Coordination Information and configuration parameters application in CPAC | Google Inc. |
| R3-222031 | (TPs to CPAC BLCR for TS36.423 and TS38.423) Handling of SN to MN Container in CPAC | Google Inc. |
| R3-222140 | [Draft] Reply LS on CPAC | Lenovo, Motorola Mobility |
| R3-222158 | (TP to CPAC BL CR for TS 37.340) SN initiated inter-SN CPC | Huawei |
| R3-222159 | (TP to CPAC BL CRs for TS38.425, 38.401) Leftover issues for CPAC | Huawei |
| R3-222204 | (TPs to CPAC BLCR for TS38.423 and TS37.340) Further Consideration on SN initiated CPC | CATT |
| R3-222221 | Reply LS on SN initiated CPC | CATT |
| R3-222233 | (TP to CPAC TS 37.340 BL CR) RAN3 signalling aspect for the SN Initiated Inter-SN CPC | NEC |
| R3-222234 | (TP to CPAC TS 38.423 BL CR) RAN3 signalling aspect for the SN Initiated Inter-SN CPC | NEC |
| R3-222235 | (TP to CPAC TS 36.423 BL CR) RAN3 signalling aspect for the SN Initiated Inter-SN CPC | NEC |
| R3-222336 | Remaining issues on the CPAC procedure | Samsung |
| R3-222337 | (TP to CPAC BL CR on TS 38.423) Early data transmission stop in the Xn-U Address Indication message | Samsung |
| R3-222346 | (TP to CPAC BL CR for TS 38.423) Preparation of Multiple T-SNs in SN initiated inter-SN CPC | Huawei |
| R3-222431 | CB: # MRDC3_CPAC - Summary of email discussion | Ericsson - moderator |
| R3-222558 | CB: # MRDC3_CPAC - Summary of email discussion | Ericsson - moderator |
| R3-222754 | Reply LS on CPAC | Lenovo, Motorola Mobility |
| R3-222780 | (TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Further development of the CPAC | Nokia, Nokia Shanghai Bell, Google |
| R3-222781 | (TP for CPAC BL CR to TS 38.423) Resolving the remaining issues for CPAC | Ericsson, Lenovo, Motorola Mobility, Google Inc. |
| R3-222782 | (TP to CPAC BL CR for TS 37.340) SN initiated inter-SN CPC | Huawei, Ericsson |
| 15.1 | General | |
| R3-221535 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson, Samsung |
| R3-221560 | BLCR to 38.300 | China Unicom, Ericsson, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-221561 | BLCR to 38.410: Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-221566 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom, Ericsson, Samsung |
| R3-221590 | (BL CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-221908 | Updated Workplan for Rel-17 NR QoE | China Unicom |
| R3-222227 | (TP for NR QoE for BL CR 38.413) Rapporteur corrections and clean-ups | Huawei |
| R3-222438 | CB: # QoE1_Workplan_BLCRs - Summary of email discussion | China Unicom - moderator |
| R3-222518 | (BL CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-222626 | LS Reply on SA4 requirements for QoE | SA4 |
| R3-222742 | BLCR to 38.300 | China Unicom, Ericsson, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-222939 | (BL CR for TS 38.401) Support of the alignment of MDT and QoE | ZTE, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-222940 | BLCR to 38.300 | China Unicom, Ericsson, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung, CATT |
| R3-222941 | BLCR to 38.410: Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-222942 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom, Ericsson, Samsung, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-222943 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson, Samsung, CATT, Huawei, ZTE, Nokia and Nokia Shanghai Bell |
| R3-222944 | (BL CR for TS38.473) Support of QoE information transfer | Samsung, Huawei, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222978 | BLCR to TS38.470 for NR QoE | China Unicom, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| 15.2.1.1 | Configuration, Activation and Deactivation Procedures | |
| R3-221676 | (TP for QoE BL CR for TS 38.300) Stage-2 Aspects of NR QoE Management | Ericsson |
| R3-222278 | (TP for BL CR to TS38.300) Support of NR QoE | Samsung |
| R3-222365 | (TP to BL CR of TS38.300) Consideration on NR QoE Configuration | ZTE |
| R3-222439 | CB: # QoE2_Stage2 - Summary of email discussion | Samsung - moderator |
| R3-222499 | (TP for QoE BL CR for TS 38.300) Stage-2 Aspects of NR QoE Management | Ericsson |
| R3-222649 | BLCR to 38.420: Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-222650 | TP for BL CR to 38.410 Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-222651 | TP for BL CR to 38.401 Support of the alignment of MDT and QoE | Samsung, Ericsson, ZTE |
| R3-222875 | LS on RAN3 agreements for NR QoE | China Unicom |
| R3-222887 | (TP for QoE BL CR for TS 38.300) Stage-2 Aspects of NR QoE Management | Ericsson |
| R3-222888 | (TP for QoE BL CR for TS 38.300) Stage-2 Aspects of NR QoE Management | Ericsson, Samsung, ZTE, CATT, Nokia |
| R3-222889 | TP for BL CR to 38.410 Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-222890 | LS on RAN3 agreements for NR QoE | China Unicom |
| 15.2.1.2 | Configuration Details | |
| R3-221670 | LS on the specification of AT commands for NR QoE | RAN2 |
| R3-221671 | Reply LS on maximum container size for QoE configuration and report | RAN2 |
| R3-221677 | (TP for QoE BL CR for TS 38.413) QoE Configuration and Reporting | Ericsson |
| R3-222107 | (TP for BL CR to TS 38.413) NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-222205 | (TP for 38.413) Discussion on NR QoE configuration procedures | CATT |
| R3-222206 | Discussion on NR QoE configuration details | CATT |
| R3-222222 | Further discussion on configuration details | Huawei |
| R3-222223 | TP to 38.413 on configuration details | Huawei |
| R3-222440 | CB: # QoE3_Configuration_Report - Summary of email discussion | Ericsson - moderator |
| R3-222501 | TP for the QOE BL CR for TS 38.413 | Huawei |
| R3-222507 | (TP for QoE BL CR for TS 38.413) QoE Configuration and Reporting | Ericsson |
| R3-222627 | LS Reply on maximum container size for QoE configuration and report | SA4 |
| R3-222629 | LS Reply on QoE configuration and reporting related issues | SA4 |
| R3-222829 | LS on the specification of AT commands for NR QoE | CT1 |
| R3-222891 | TP for the QOE BL CR for TS 38.413 | Huawei, Ericsson |
| 15.2.2 | Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | |
| R3-221678 | (TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-221752 | Open issues regarding QMC and reporting continuity in mobility scenarios | Qualcomm Incorporated |
| R3-221863 | (TP for BL CR to TS 38.423) Handling of m-based MDT in case of mobility | Nokia, Nokia Shanghai Bell |
| R3-221931 | Further discussion on Mobility of QoE measurement | China Unicom |
| R3-222151 | Discussion on remaining issues in NR QoE mobility | ZTE Corporation |
| R3-222178 | Discussion on remaining issues in NR QoE mobility | ZTE Corporation |
| R3-222207 | Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | CATT |
| R3-222224 | Further discussions on mobility support of QoE measurement | Huawei |
| R3-222279 | (TP for BL CR to TS 38.423) Mobility support of NR QoE | Samsung |
| R3-222386 | Transfer of QMC information during handover | Nokia, Nokia Shanghai Bell |
| R3-222441 | CB: # QoE4_Mobility - Summary of email discussion | Huawei - moderator |
| R3-222624 | (TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-222812 | (TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-222886 | (TP for QoE BL CR for TS 38.423) Mobility Support for NR QoE Measurement Collection | Ericsson, Huawei |
| 15.3 | Support for RAN-Visible QoE | |
| R3-221672 | Reply LS on RAN visible QoE | RAN2 |
| R3-221679 | The Remaining Issues for RAN Visible QoE | Ericsson |
| R3-221753 | Open issues regarding RAN visible QoE | Qualcomm Incorporated |
| R3-221864 | Remaining open points on RAN visible QoE | Nokia, Nokia Shanghai Bell |
| R3-221909 | (TP for QoE BL CR for TS 38.423) RAN visible QoE for NR QoE Measurement Collection | China Unicom |
| R3-222208 | Discussion on RAN visible QoE configuration and reporting | CATT |
| R3-222225 | Further discussions on RAN visible QoE metrics | Huawei |
| R3-222263 | Leftover issues on RVQoE | CMCC |
| R3-222280 | (TP for BL CR to TS 38.473) RAN visible QoE | Samsung |
| R3-222366 | Further consideration on RVQoE | ZTE |
| R3-222442 | CB: # QoE5_RVQoE - Summary of email discussion | Qualcomm - moderator |
| R3-222628 | LS Reply on RAN visible QoE | SA4 |
| R3-222751 | (TP for BL CR to TS 38.473) RAN visible QoE | Samsung |
| R3-222759 | Reply LS on RAN visible QoE | Ericsson |
| R3-222793 | Reply LS on RAN visible QoE | Ericsson |
| R3-222794 | (TP for BL CR to TS 38.473) RAN visible QoE | Samsung |
| R3-222813 | Reply LS on RAN visible QoE | Ericsson |
| R3-222892 | (TP for BL CR to TS 38.473) RAN visible QoE | Samsung |
| 15.4 | Alignment of Radio-Related Measurement and QoE Measurements | |
| R3-221680 | (TP for QoE BL CR for TS 38.300) The Alignment of Radio-related Measurements and QoE Measurements | Ericsson |
| R3-221754 | Open issues regarding MDT-QoE alignment | Qualcomm Incorporated |
| R3-221865 | Remaining open points on QMC/MDT alignment | Nokia, Nokia Shanghai Bell |
| R3-221929 | Further discussion on alignment of MDT and QoE Measurements | China Unicom |
| R3-222209 | Discussion on Alignment of MDT and QoE Measurements | CATT |
| R3-222226 | Further discussions on alignment between QoE measurement and MDT measurement | Huawei |
| R3-222281 | (TP for BL CR to TS 38.473 and TS 38.463) Alignment of MDT and QoE | Samsung |
| R3-222282 | (TP for BL CR to TS38.401) Alignment of MDT and QoE | Samsung |
| R3-222367 | Further consideration on MDT alignment | ZTE, China Telecom |
| R3-222368 | Further discussion on MDT alignment in Split architecture | ZTE |
| R3-222369 | (TP for BL CR of TS38.463) Alignment of MDT and QoE Measurements | ZTE, China Unicom, China Telecom |
| R3-222370 | (TP for BL CR of TS38.473) Alignment of MDT and QoE Measurements | ZTE, China Unicom, China Telecom |
| R3-222443 | CB: # QoE6_MDTAlignment - Summary of email discussion | ZTE - moderator |
| R3-222770 | TP to BL CR of 38.413 on MDT alignment | ZTE |
| 16.1 | General | |
| R3-221518 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-221542 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-221543 | Supporting enhanced private network | Huawei |
| R3-221710 | Work Plan for Enhancement for Private Network Support for NG-RAN WI | China Telecommunication |
| R3-222467 | CB: # NPN1_Workplan_BLCRs - Summary of email discussion | China Telecom - moderator |
| 16.2.1 | Cell Access Control | |
| R3-221711 | (TP for TS 38.473) Support for eNPN | China Telecommunication |
| R3-221812 | (TP for TS 38.300) Conclusions on onboarding open points | Nokia, Nokia Shanghai Bell |
| R3-221970 | Supporting enhanced private network | Huawei |
| R3-222056 | Congestion control for UE onboarding | Ericsson |
| R3-222248 | Left issues on enhanced NPN | ZTE Corporation |
| R3-222468 | CB: # NPN2_CellAccessControl - Summary of email discussion | Nokia - moderator |
| 17.1 | General | |
| R3-221526 | Support of Enhanced RAN Slicing | Nokia, Nokia Shanghai Bell |
| R3-221527 | Supporting network slicing enhancement | Huawei |
| R3-221598 | BLCR to 38.463: Support of slicing enhancement | Ericsson, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Huawei, CATT |
| R3-221602 | (BLCR to TS 38.473) Supporting network slicing enhancement | ZTE, Nokia, Nokia Shanghai Bell, Huawei, CATT, Ericsson, Samsung |
| R3-221603 | (BL CR to TS38.423) RAN slicing enhancement | Samsung, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT, Ericsson |
| R3-221604 | (BLCR to 37.340) Enhancement of RAN Slicing | CATT, ZTE, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R3-222261 | Updated work plan for RAN slicing | CMCC, ZTE |
| R3-222444 | CB: # RANSlicing1_Workplan_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-222455 | Response to R3-221527 | Ericsson-LG Co., LTD |
| R3-222546 | Supporting network slicing enhancement | Huawei |
| R3-222954 | Support of Enhanced RAN Slicing | Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-222979 | Supporting network slicing enhancement | Huawei, Nokia, Nokia Shanghai Bell |
| 17.2 | Support Service Continuity | |
| R3-221813 | (TP for TS38.300 and TS38.423) Handling of Slicing resource shortage | Nokia, Nokia Shanghai Bell |
| R3-221964 | (TP for NR_Slice BLCR for TS 38.300) Supporting Service Continuity | Huawei |
| R3-221966 | (TP for NR_Slice BLCR for TS 38.413 and TS 38.423) Impact of slice-aware cell reselection | Huawei |
| R3-222093 | Addition of an SCG outside the serving TA | Ericsson |
| R3-222193 | Leftover issue for support Service Continuity | ZTE |
| R3-222262 | Leftover issues to support slice based cell reselection and RACH | CMCC |
| R3-222283 | (TP for BL CR to TS 38.300) Support of Service Continuity | Samsung |
| R3-222445 | CB: # RANSlicing2_Service_Continuity - Summary of email discussion | Nokia - moderator |
| R3-222562 | CB: # RANSlicing2_Service_Continuity - Summary of email discussion | Nokia - moderator |
| R3-222665 | (TP for TS38.300) Handling of Slicing resource shortage | Nokia, Nokia Shanghai Bell |
| R3-222694 | Reply LS on Slice list and priority information for cell reselection | SA2 |
| R3-222738 | Reply LS on Clarification of SCG outside RA for slicing | SA2 |
| 17.3 | Support the Enforcement of Slice MBR | |
| R3-221814 | (TP for TS 38.473) Support for Slice Maximum Bit Rate | Nokia, Nokia Shanghai Bell |
| R3-221815 | (TP for TS 38.463) Support of Slice Maximum Bit Rate | Nokia, Nokia Shanghai Bell |
| R3-221965 | (TP for NR_Slice BLCR for TS 38.413) Remaining issues on SA2 impact | Huawei |
| R3-222091 | (TP for NR_Slice BLCR for for TS 38.413) Way forward on Target NSSAI Handling in RAN | Ericsson, Deutsche Telekom, Orange, Vodafone |
| R3-222092 | LS on S-MBR and Target NSSAI | Ericsson |
| R3-222194 | Leftover issue of Impact on RAN slicing of UE slice MBR and Target NSSAI | ZTE |
| R3-222195 | (TP for NR_Slice for TS 38.413) Supporting network slicing enhancement | ZTE |
| R3-222210 | Discussion on Supporting for Target NSSAI | CATT |
| R3-222211 | TP to 38.413 for Target NSSAI | CATT |
| R3-222242 | Further discussion on inclusion of Target NSSAI in NGAP | LG Electronics |
| R3-222284 | Support of Target NSSAI | Samsung |
| R3-222446 | CB: # RANSlicing3_UESliceMBR - Summary of email discussion | ZTE - moderator |
| R3-222506 | (TP for NR_Slice BLCR for for TS 38.413) Way forward on Target NSSAI Handling in RAN | Ericsson, Deutsche Telekom, Orange, Vodafone, Bell Mobility |
| R3-222563 | CB: # RANSlicing3_UESliceMBR - Summary of email discussion | ZTE - moderator |
| 18.1 | General | |
| R3-221610 | TR37.817 v1.2.0 | CMCC |
| R3-221941 | Consideration on alignment for AIML in NG-RAN Rel-17 SI | Intel Corporation |
| R3-222276 | TP to TR 37 817 for SI conclusion | CMCC |
| R3-222447 | CB: # AIRAN1_General - Summary of email discussion | CMCC - moderator |
| R3-222764 | TP to TR 37.817 for SI Conclusion | CMCC |
| R3-222969 | TR37.817 v1.3.0 | CMCC |
| R3-222989 | TR37.817 v1.4.0 | CMCC |
| 18.2 | High-Level Principles and Definitions | |
| R3-221779 | Proposed updates to High-Level Principles | NEC |
| R3-221985 | (TP to TR 37.817) On high-level principles | Lenovo, Motorola Mobility |
| R3-222017 | (TP for TR 37.817) Clarification on Inference Data | CATT |
| R3-222030 | Discussion on some remaining issues for alignment of sections within TR 37.817 (incl. TP) | Deutsche Telekom |
| R3-222100 | (TP for BL CR for TR 37.817) Framework for RAN intelligence | Ericsson |
| R3-222120 | (TP for TR 37.817) AI/ML Framework final remarks | Nokia, Nokia Shanghai Bell |
| R3-222231 | Further discussions on framework | Huawei |
| R3-222243 | Clean FFS for AI Functional Framework for RAN Intelligence | ZTE Corporation |
| R3-222270 | Clean up of AI_ML framework | CMCC |
| R3-222308 | Discussion on Functional Framework and High-Level Principles | Samsung |
| R3-222448 | CB: # AIRAN2_Framework - Summary of email discussion | Nokia - moderator |
| R3-222653 | (TP for TR 37.817) General Framework | Nokia - moderator |
| R3-222798 | (TP for TR 37.817) General Framework | Nokia - moderator |
| 18.4.1 | Network Energy Saving | |
| R3-221695 | Closing open issues in AI/ML Energy Savings use case | InterDigital Finland Oy |
| R3-221780 | Proposed updates to Energy Saving Solutions and Standard Impact | NEC |
| R3-221848 | Network energy saving | Qualcomm Incorporated |
| R3-221942 | AI/ML based network energy saving | Intel Corporation |
| R3-221986 | (TP to TR 37.817) On Network Energy Saving | Lenovo, Motorola Mobility |
| R3-222018 | (TP for TR 37.817)Discussion on Standards Impact on energy saving | CATT |
| R3-222101 | (TP for BL CR for TR 37.817) Network Energy Saving | Ericsson |
| R3-222121 | (TP for TR 37.817) A few final aspects on AI/ML Energy Saving | Nokia, Nokia Shanghai Bell |
| R3-222228 | Further discussions on energy saving | Huawei |
| R3-222244 | Further discussion on solution to AI based Network Energy Saving | ZTE Corporation |
| R3-222274 | On Remaining issues for AI based Energy Saving | CMCC |
| R3-222309 | Discussion on Standard Impact for AI/ML based Network Energy Saving | Samsung |
| R3-222328 | Further discussion for AI-based network energy saving | China Telecom Corporation Ltd. |
| R3-222449 | CB: # AIRAN3_ES - Summary of email discussion | ZTE - moderator |
| R3-222718 | TP to 37.817 on AI/ML based network energy saving | ZTE |
| R3-222800 | TP to 37.817 on AI/ML based network energy saving | ZTE |
| 18.4.2 | Load Balancing | |
| R3-221696 | Closing open issues in AI/ML Load Balancing use case | InterDigital Finland Oy |
| R3-221781 | Proposed updates to Load Balancing Solutions and Standard Impact | NEC |
| R3-221847 | Load balancing | Qualcomm Incorporated |
| R3-221943 | AI/ML based load balancing | Intel Corporation |
| R3-221987 | (TP to TR 37.817) On Load Balancing | Lenovo, Motorola Mobility |
| R3-222019 | (TP for TR 37.817)Discussion on Standards Impact on load balancing | CATT |
| R3-222045 | AI/ML-based Load Balancing – Discussions on remaining open issues | Futurewei |
| R3-222122 | (TP for TR 37.817) Final Discussions in AI/ML Load Balancing | Nokia, Nokia Shanghai Bell |
| R3-222230 | Further discussions on load balancing | Huawei |
| R3-222245 | Further discussion on solution to AI based load balancing | ZTE Corporation |
| R3-222273 | On Remaining issues for AI based Load Balancing | CMCC |
| R3-222310 | Discussion on Standard Impact for AI/ML based Load Balancing | Samsung |
| R3-222329 | Discussion on input and output for AI-based load balancing | China Telecom Corporation Ltd. |
| R3-222450 | CB: # AIRAN4_LBSolution - Summary of email discussion | InterDigital - moderator |
| R3-222708 | (TP to TR 37.817) Closing open issues on Load Balancing | InterDigital |
| R3-222801 | (TP to TR 37.817) Closing open issues on Load Balancing | InterDigital |
| R3-222865 | (TP to TR 37.817) Closing open issues on Load Balancing | InterDigital |
| 18.4.3 | Mobility Optimization | |
| R3-221697 | Closing open issues in AI/ML Mobility Optimization use case | InterDigital Finland Oy |
| R3-221846 | Mobility optimization | Qualcomm Incorporated |
| R3-221944 | AI/ML based mobility optimization | Intel Corporation |
| R3-221988 | (TP to TR 37.817) On Mobility Optimization | Lenovo, Motorola Mobility |
| R3-222020 | (TP for TR 37.817) Discussion on Standards Impact on Mobility | CATT |
| R3-222047 | AI/ML-based Mobility Optimization – Discussions on remaining open issues | Futurewei |
| R3-222102 | (TP for BL CR for TR 37.817) AIML Load Balancing and Mobility Optimisation use cases | Ericsson |
| R3-222123 | (TP for TR 37.817) Addressing Remaining Open Aspects in AI/ML Mobility Optimization | Nokia, Nokia Shanghai Bell |
| R3-222229 | Further discussions on mobility | Huawei |
| R3-222246 | Further discussion on solution to AI based Mobility Optimization | ZTE Corporation |
| R3-222275 | On Remaining issues for AI based Mobiliy Optimization | CMCC |
| R3-222311 | Discussion on Standard Impact for AI/ML based Mobility Optimization | Samsung |
| R3-222330 | Input and output for AI-based mobility optimization | China Telecom Corporation Ltd. |
| R3-222451 | CB: # AIRAN5_Mobility - Summary of email discussion | Futurewei - moderator |
| R3-222655 | TP to 37.817 on AI/ML based Mobility Optimization | Futurewei |
| R3-222805 | TP to 37.817 on AI/ML based Mobility Optimization | Futurewei |
| R3-222816 | CB: # AIRAN5_Mobility - Summary of email discussion | Futurewei - moderator |
| R3-222866 | TP to 37.817 on AI/ML based Mobility Optimization | Futurewei |
| 19.1 | General | |
| R3-221558 | Introduction of NR Positioning enhancements to NRPPa | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221559 | Introduction of NR Positioning enhancements | Huawei |
| R3-221570 | Introduction of release 17 positioning enhancements | Qualcomm Incorporated |
| R3-221605 | (BL CR to TS 38.423) Transfer of Positioning Context in XnAP | CATT |
| R3-222432 | CB: # 1901_Pos_BLCRs - Summary of email discussion | Ericsson - moderator |
| R3-222542 | LS to RAN1 on positioning issues needing further input | RAN2 |
| R3-222672 | Introduction of NR Positioning enhancements | Huawei, Ericsson |
| R3-222676 | (BL CR to TS 38.423) Transfer of Positioning Context in XnAP | CATT, Ericsson, Huawei |
| R3-222719 | Introduction of release 17 positioning enhancements | Qualcomm Incorporated, Ericsson, Huawei |
| R3-222935 | Introduction of NR Positioning enhancements | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-222936 | Introduction of NR Positioning enhancements to NRPPa | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222937 | Introduction of release 17 positioning enhancements | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222938 | (BL CR to TS 38.423) Transfer of Positioning Context in XnAP | CATT, Ericsson, Huawei |
| 19.2.1 | Positioning Accuracy Improvements | |
| R3-221657 | LS on SRS for multi-RTT positioning | RAN4 |
| R3-221658 | Reply LS on reporting of the Tx TEG association information | RAN4 |
| R3-221663 | Response LS on the reporting of the Tx TEG association information | RAN2 |
| R3-221746 | (TP for NRPPa baseline) TRP Beam Antenna Information | Qualcomm Incorporated |
| R3-221880 | (TP for POS BL CR for TS 38.455) on Positioning accuracy improvement | Huawei |
| R3-221892 | (TP for Positioning BLCRs) Further Consideration on Accuracy Improvement | CATT |
| R3-221945 | (TP to NRPPA BL CR): addressing remaining open points on Positioning Accuracy Improvements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221946 | (TP to F1AP BL CR): addressing remaining open points on Positioning Accuracy Improvements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221947 | (TP to NRPPA BL CR): proposals for overhead reduction in NRPPa and F1AP | Ericsson |
| R3-222333 | (TP for POS BL CR for TS 38.473) on Positioning accuracy improvement | Huawei |
| R3-222433 | CB: # 1902_Pos_Acc_Imp - Summary of email discussion | Ericsson - moderator |
| R3-222456 | Response paper to R3-221746 and R3-221880 | Ericsson-LG Co., LTD |
| R3-222630 | (TP to NRPPA BL CR): addressing remaining open points on Positioning Accuracy Improvements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222631 | (TP to F1AP BL CR): addressing remaining open points on Positioning Accuracy Improvements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222656 | Questions concerning the implementation of RAN1 agreements in NRPPa | Ericsson |
| R3-222660 | Reply LS on SRS for multi-RTT positioning | RAN1 |
| R3-222720 | (TP to NRPPA BL CR): addressing remaining open points on Positioning Accuracy Improvements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222721 | Questions concerning the implementation of RAN1 agreements in NRPPa | Ericsson |
| R3-222722 | (TP for NRPPa baseline) TRP Beam Antenna Information | Qualcomm Incorporated |
| R3-222723 | CB: # 1902_Pos_Acc_Imp - Summary of email discussion | Ericsson - moderator |
| R3-222767 | (TP for F1AP baseline) TRP Beam Antenna Information | Qualcomm Incorporated, Ericsson |
| 19.2.2 | RRC_INACTIVE State Positioning | |
| R3-221659 | LS on DRX cycle used in PRS measurement in RRC_INACTIVE state | RAN4 |
| R3-221747 | (TP for NRPPa baseline) LMF Assistance Information to support positioning in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-221881 | (TP for POS BL CR for TS 38.455, TS 38.473) on RRC_INACTIVE positioning | Huawei |
| R3-221893 | (TP for Positioning BL CR 38.423) Positioning support in Inactive | CATT |
| R3-221948 | (TP for NRPPa BL CR on Positioning) Completion of RRC_INACTIVE assistance data for positioning | Ericsson |
| R3-222257 | Discussion on RRC INACTIVE State Positioning | CMCC |
| R3-222285 | Positioning in RRC inactive state | Samsung |
| R3-222286 | (TP for BL CR TS38.423) RRC Inactive positioning | Samsung |
| R3-222287 | (TP for BL CR TS38.473) RRC Inactive positioning | Samsung |
| R3-222342 | Discussion on RRC_INACTIVE state Positioning | VIVO TECH GmbH |
| R3-222434 | CB: # 1903_Pos_RRC_INACTIVE - Summary of email discussion | Samsung - moderator |
| R3-222657 | (TP for NRPPa BL CR on Positioning) Completion of RRC_INACTIVE assistance data for positioning | Ericsson |
| R3-222658 | (TP for F1AP BL CR on Positioning) Completion of RRC_INACTIVE assistance data for positioning | Ericsson |
| R3-222670 | (TP for Positioning BL CR 38.423) Positioning support in Inactive | CATT, Samsung |
| R3-222671 | (TP for BL CR TS38.473) RRC Inactive positioning | Samsung, CATT |
| 19.2.3 | On-Demand PRS Transmission and Reception | |
| R3-221871 | (TP for NR_pos_enh BL CR for TS 38.455) Resolution of open issues for on-demand PRS | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-221872 | (TP for NR_pos_enh BL CR for TS 38.473) Resolution of open issues for on-demand PRS | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-221873 | Introduction of NR positioning enhancements to NGAP | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-221882 | (TP for POS BL CR for TS 38.455, TS 38.473)On-demand PRS, ON/OFF Granularity | Huawei |
| R3-221894 | (TP for Positioning BLCRs) Further Consideration on On-Demand PRS | CATT |
| R3-222435 | CB: # 1904_Pos_OnDemandPRS - Summary of email discussion | Nokia - moderator |
| R3-222611 | (TP for NR_pos_enh BL CR for TS 38.455) Resolution of open issues for on-demand PRS | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-222612 | (TP for NR_pos_enh BL CR for TS 38.473) Resolution of open issues for on-demand PRS | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| 19.2.5 | Information Reporting for Multipath and NLOS Mitigation | |
| R3-221748 | (TP for NRPPa baseline) Path Power for Additional Paths | Qualcomm Incorporated |
| R3-221883 | (TP for POS BL CR for TS 38.455, TS 38.473) correction Multipath and NLOS | Huawei |
| R3-222436 | CB: # 1905_Pos_Multipath_NLOS - Summary of email discussion | Qualcomm - moderator |
| R3-222668 | (TP for POS BL CR for TS 38.455) correction Multipath and NLOS | Huawei |
| R3-222669 | (TP for POS BL CR for TS 38.473) correction Multipath and NLOS | Huawei |
| 19.3 | Support for Latency Improvement | |
| R3-221674 | Reply LS on latency improvement for PRS measurement with MG | RAN2 |
| R3-221884 | (TP for POS BL CR for TS 38.455) Remaining Open Issues on Positioning Latency Improvement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-221895 | (TP for Positioning BLCRs) Latency Improvement for PRS Measurement | CATT |
| R3-221949 | Discussion on positioning PRS processing window signalling and latency gain aspects | Ericsson |
| R3-222200 | (TP for POS BL CR for TS 38.473) Remaining Open Issues on Positioning Latency Improvement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222341 | Discussion on Latency enhancements | VIVO TECH GmbH |
| R3-222385 | Discussion on latency improvement | ZTE Corporation |
| R3-222437 | CB: # 1906_Pos_LatencyImprovement - Summary of email discussion | Huawei - moderator |
| R3-222737 | Response LS on determination of location estimates in local co-ordinates | SA2 |
| R3-222768 | Discussion on positioning PRS processing window signalling and latency gain aspects | Ericsson |
| R3-222788 | (TP for POS BL CR for TS 38.455) Remaining Open Issues on Positioning Latency Improvement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-222789 | (TP for POS BL CR for TS 38.473) Remaining Open Issues on Positioning Latency Improvement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-222790 | (TP for POS BL CR for TS 38.470) Positioning Latency Improvement | Huawei, Ericsson, CATT |
| R3-222834 | CB: # 1906_Pos_LatencyImprovement - Summary of email discussion | Huawei - moderator |
| 20.1 | General | |
| R3-221508 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, Thales |
| R3-221509 | Introduction of NTN | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-221524 | Introduction of NTN | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-221609 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| R3-221662 | Reply LS on NTN specific User Consent | RAN2 |
| R3-221675 | LS on UE location during initial access in NTN | RAN2 |
| R3-221742 | (TP for TS 38.300 BL CR on NTN) Discussion of the RAN2 LS on absence of UE location information at RRC Setup | Qualcomm Incorporated |
| R3-221743 | (TP for TS38.413 BL CR on NTN) LS Response Analysis: Handling TA reporting in ULI | Qualcomm Incorporated |
| R3-221770 | LS response on UE location during initial access in NTN | THALES |
| R3-221786 | UE Location Information and NTN | Ericsson LM |
| R3-221787 | [DRAFT] Reply LS on UE location during initial access in NTN | Ericsson LM |
| R3-221797 | CHO for NTN - Possible RAN3 Impacts of Ongoing RAN2 Discussion | Ericsson LM, Thales |
| R3-221921 | UE location report during initial access | Huawei |
| R3-221922 | [DRAFT] Relpy LS on UE location during initial access in NTN | Huawei |
| R3-222469 | CB: # 2001_NTN_General - Summary of email discussion | Thales - moderator |
| R3-222619 | LS Response to LS on UE location during initial access in NTN | SA2 |
| R3-222620 | LS on Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | SA2 |
| R3-222693 | LS on Reply LS on UE location aspects in NTN | SA2 |
| R3-222732 | CB: # 2001_NTN_General - Summary of email discussion | Thales - moderator |
| R3-222733 | LS on UE location during initial access in NTN | Thales |
| R3-222736 | Reply LS on UE Location Aspects in NTN | SA2 |
| R3-222785 | New TAC structure | Huawei |
| R3-222795 | Reply LS on UE location during initial access in NTN | Thales |
| R3-222796 | CB: # 2001_NTN_General - Summary of email discussion | Thales - moderator |
| R3-222830 | NR satellite RAT type in UE NAS | CT1 |
| R3-222861 | Reply LS on UE location during initial access in NTN | Thales |
| R3-222862 | New TAC structure | Huawei |
| R3-222933 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-222934 | Introduction of NTN | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| 21.1 | General | |
| R3-221552 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-221553 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| R3-221554 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-221555 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| R3-222452 | CB: # NRIIOT1_BL CRs - Summary of email discussion | ZTE - moderator |
| R3-222539 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-222540 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| R3-222541 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-222924 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| 21.2 | Support for Propagation Delay Compensation Enhancements | |
| R3-221666 | LS on PDC for Time Synchronization | RAN2 |
| R3-221874 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.473) Time synchronization: resolution of F1AP open issues | Nokia, Nokia Shanghai Bell |
| R3-221875 | Time synchronization: resolution of mobility open issues | Nokia, Nokia Shanghai Bell |
| R3-221877 | Discussion on Time Synchronization enhancements | ZTE |
| R3-221878 | (TP for Introduction of Enhanced IIoT support over F1) Time Synchronization enhancements | ZTE |
| R3-221951 | Propagation Delay Compensation for TSN time synchronization | NTT DOCOMO INC. |
| R3-221967 | (TP for eIIOT BLCR for TS 38.473 and TS 38.423) Supporting PDC enhancements: TA-based PDC and mobility | Huawei |
| R3-221968 | (TP for eIIOT BLCR for TS 38.473) Supporting PDC enhancements: RTT based PDC | Huawei |
| R3-222037 | Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization | Ericsson |
| R3-222038 | Discussion on PDC TA based and E-CID measurement | Ericsson |
| R3-222212 | Discussion on Propagation Delay Compensation Enhancements | CATT |
| R3-222213 | TP for BLCR for 38.473 on Propagation Delay Compensation Enhancements | CATT |
| R3-222453 | CB: # NRIIOT2_PDC - Summary of email discussion | Nokia - moderator |
| R3-222560 | CB: # NRIIOT2_PDC - Summary of email discussion | Nokia - moderator |
| R3-222561 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.473) Time synchronization: resolution of F1AP open issues | Nokia, Nokia Shanghai Bell |
| R3-222581 | Introduction of Propagation Delay Compensation Procedure | Huawei |
| 21.3 | Enhancements Based on New QoS Related Parameters | |
| R3-221876 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Resolution of open issues for Survival Time | Nokia, Nokia Shanghai Bell |
| R3-221879 | (TP for Introduction of Enhanced IIoT support over Xn and F1) Remaining issues on New QoS Related parameters | ZTE |
| R3-221969 | (TP for eIIOT BLCR for TS 38.423 and TS 38.425) Survival time remaining issues | Huawei |
| R3-222039 | On survival time | Ericsson |
| R3-222214 | Discussion on new QoS related parameters | CATT |
| R3-222454 | CB: # NRIIOT3_NewQoS - Summary of email discussion | Huawei - moderator |
| 22.1 | General | |
| R3-221502 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-221503 | Introduction of NR MBS | Lenovo, Motorola mobility |
| R3-221506 | Introduction of NR MBS | Samsung R&D Institute UK |
| R3-221507 | Introduction of NR MBS | LG Electronics |
| R3-221521 | Introduction of NR MBS | Huawei, CMCC |
| R3-221522 | BL CR for NR MBS for 38.413 | Qualcomm Incorporated, Huawei |
| R3-221523 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-221525 | BL CR to TS38.420 | CMCC |
| R3-221556 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-221557 | MBS BL CR for TS38.410 | ZTE |
| R3-222160 | Rapporteur clean-up for TS 38.401 BL CR | Huawei |
| R3-222470 | CB: # MBS1_General - Summary of email discussion | CATT - moderator |
| R3-222535 | CB: # MBS1_General - Summary of email discussion | CATT - moderator |
| R3-222589 | Summary of Offline Discussion on a potential overall compromise for NR MBS Rel-17 | Ericsson |
| R3-222590 | [Draft] LS on further outstanding issues in TS 23.247 | Ericsson |
| R3-222593 | Way Forward on Rel-17 NR MBS WI | Huawei, CATT, Lenovo, Motorola Mobility |
| R3-222595 | WF on Rel-17 NR MBS WI | ZTE |
| R3-222597 | Way forward for MBS compromise | Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Motorola Mobility |
| R3-222625 | [Draft] LS on further outstanding issues in TS 23.247 | Ericsson |
| R3-222804 | TP for 38.300, clean up of editors’ note | Nokia, Nokia Shanghai Bell |
| R3-222823 | Rapporteur clean-up for TS 38.401 BL CR | Huawei |
| R3-222867 | LS on further outstanding issues in TS 23.247 | Ericsson |
| R3-222925 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-222926 | Introduction of NR MBS | Huawei, CMCC, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-222927 | BL CR for NR MBS for 38.413 | Qualcomm Incorporated, Huawei, Ericsson |
| R3-222928 | Introduction of NR Multicast and Broadcast Services | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222929 | Introduction of NR MBS | LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-222930 | Introduction of MBS(BL CR for 38.463) | CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-222931 | Introduction of NR MBS | Lenovo, Motorola mobility, Nokia, Nokia Shanghai Bell |
| R3-222932 | Introduction of NR MBS | Samsung, Nokia, Nokia Shanghai Bell, Ericsson |
| 22.2.2 | Session Management over NG | |
| R3-221654 | LS on MBS session restoration for NG-RAN failure with or without restart | CT4 |
| R3-222021 | (TP for 38.413) MBS session management for broadcast | CATT |
| R3-222023 | Discussion on MBS session management for multicast | CATT |
| R3-222059 | [TP for BL CR 38.413] Comments on MBS Session Management | Ericsson |
| R3-222076 | (TP for 38.413) Correct Handling of Broadcast MB-SMF containers | Nokia, Nokia Shanghai Bell |
| R3-222078 | (TP for 38.413) NGAP Correction for MBS Group Paging | Nokia, Nokia Shnaghai Bell |
| R3-222079 | (TP for 38.423) XnAP Correction for MBS Group Paging | Nokia, Nokia Shanghai Bell |
| R3-222152 | (TP for TS38300) Discussion on MBS session management | ZTE Corporation |
| R3-222161 | (TP to 38.413 BL CR) Leftover issues on session management | Huawei, CBN, China Unicom, China Telecom |
| R3-222174 | (TP to TS 38.300 BL CR) On Note 4 for TS 23.247 section 7.2.1.3 | Huawei, CBN |
| R3-222179 | (TP for TS38300) Discussion on MBS session management | ZTE Corporation |
| R3-222252 | MBS Session management over NG for multicast | CMCC |
| R3-222290 | (TP to BL CR for TS 38.413, 38.423) Discussion on open issues in NG | Samsung |
| R3-222416 | Response Paper to R3-222161 | Huawei |
| R3-222471 | CB: # MBS2_SessMgmt - Summary of email discussion | Nokia - moderator |
| R3-222537 | CB: # MBS2_SessMgmt - Summary of email discussion | Nokia - moderator |
| R3-222573 | LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation | CT4 |
| R3-222583 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | SA6 |
| R3-222584 | [TP for BL CR 38.413] Comments on MBS Session Management | Ericsson |
| R3-222636 | CB: # MBS2_SessMgmt - Summary of email discussion | Nokia - moderator |
| R3-222637 | (TP for 38.413) Correct Handling of Broadcast MB-SMF containers | Nokia, Nokia Shanghai Bell |
| R3-222687 | Reply LS on MBS session restoration for NG-RAN failure with or without restart | SA2 |
| R3-222688 | LS Response LS on MBS Session Management aspects | SA2 |
| R3-222714 | [TP for BL CR 38.413] Comments on MBS Session Management | Ericsson |
| R3-222727 | (TP for 38.413) MBS session management for broadcast | CATT |
| R3-222807 | (TP to 38.413 BL CR) Leftover issues on session management | Huawei, CBN, China Unicom, China Telecom |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-221698 | Bearer management for NR MBS with TP to BL CR for TS 38.425 BL CR | ZTE |
| R3-221782 | MBS MCCH over F1 | NEC |
| R3-221783 | (TP to TS 38.473 BL CR) MCCH over F1 | NEC |
| R3-221784 | F1-U tunnel for PTP leg | NEC |
| R3-221785 | (TP to TS 38.473 BL CR) F1-U tunnel for PTP leg | NEC |
| R3-221989 | (TP to TS 38.463 BL CR) Bearer Management for Multicast | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-221990 | (TP to TS 38.460 BL CR) Bearer Management for Multicast | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-221991 | Configuration of initial value of HFN and reference SN over E1AP | Lenovo, Motorola Mobility |
| R3-221992 | (TP to TS 38.425 BL CR) Remaining issues on Flow control and F1-U tunnel | Lenovo, Motorola Mobility |
| R3-222060 | [TP for BL CR 38.401] Multicast and Broadcast F1 and E1 stage 2 | Ericsson |
| R3-222061 | [TP for BL CR 38.463] Multicast and Broadcast E1AP functions | Ericsson |
| R3-222062 | [TP for BL CR 38.473] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222080 | (TP for 38.473) F1AP Correction for MBS Group Paging | Nokia, Nokia Shanghai Bell |
| R3-222081 | (TP for 38.473) F1AP full UE associated Signalling solution for Multicast | Nokia, Nokia Shanghai Bell |
| R3-222112 | Discussion on bearer management over F1/E1 for multicast | LG Electronics |
| R3-222162 | (TPs to TS 38.401 38.470, 38.460 BL CRs) Bearer management over F1 and E1 for Broadcast | Huawei, Nokia, Nokia Shanghai Bell, CBN, China Unicom, China Telecom, CMCC |
| R3-222163 | (TPs to TS 38.401, 470, 460 BL CRs) Bearer Management for Multicast | Huawei, Lenovo, Motorola Mobility, CBN, CMCC |
| R3-222164 | (TP to 38.473 BL CR) Bearer Management for Multicast | Huawei, Lenovo, Motorola Mobility, CBN, CMCC |
| R3-222165 | (TP to TS 38.425 BL CR) Flow Control for MBS | Huawei, CBN, China Unicom, China Telecom |
| R3-222253 | (TP for TS 38.425) Discussion on flow control for MBS | CMCC |
| R3-222277 | F1-U tunnel for MRB retransmission | Qualcomm Incorporated |
| R3-222291 | (TP for TS38.425): Discussion on open issues in F1 for multicast | Samsung |
| R3-222322 | Bearer management for NR MBS with TP to BL CR for TS 38.425 BL CR | ZTE |
| R3-222472 | CB: # MBS3_BearerMgmt - Summary of email discussion | Ericsson - moderator |
| R3-222494 | [TP for BL CR 38.473] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222585 | [TP for BL CR 38.401] Multicast and Broadcast F1 and E1 stage 2 | Ericsson |
| R3-222586 | [TP for BL CR 38.463] Multicast and Broadcast E1AP functions | Ericsson |
| R3-222587 | [TP for BL CR 38.473] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222596 | CB: # MBS3_BearerMgmt - Summary of email discussion | Ericsson - moderator |
| R3-222677 | CB: # MBS3_BearerMgmt - Summary of email discussion | Ericsson - moderator |
| R3-222678 | [TP for BL CR 38.401] Multicast and Broadcast F1 and E1 stage 2 | Ericsson |
| R3-222679 | [TP for BL CR 38.463] Multicast and Broadcast E1AP functions | Ericsson |
| R3-222680 | [TP for BL CR 38.473] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222755 | BLCR to TS 38.425: Introduction of MBS | Samsung, Huawei, CMCC, CBN, China Unicom, China Telecom |
| R3-222876 | BLCR to TS 38.425: Introduction of MBS | Samsung, Huawei, CMCC, CBN, China Unicom, China Telecom |
| R3-222881 | Reply LS on NR RRC to support split NR-RAN architecture for NR MBS | RAN2 |
| R3-222893 | [TP for BL CR 38.473] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222894 | [TP for BL CR 38.470] Multicast and Broadcast F1AP functions | Ericsson |
| R3-222895 | [TP for BL CR 38.463] Multicast and Broadcast E1AP functions | Ericsson |
| R3-222896 | [TP for BL CR 38.460] Multicast and Broadcast E1AP functions | Ericsson |
| 22.2.6 | Others | |
| R3-221993 | Handover Signalling for Local Multicast Session | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE |
| R3-222065 | Discussion on MBS service areas | Ericsson |
| R3-222155 | TP for 38300 on local MBS | ZTE Corporation |
| R3-222166 | (TP to TS 38.300 BL CR) Support of Local MBS | Huawei, CBN, China Unicom |
| R3-222182 | TP for 38300 on local MBS | ZTE Corporation |
| R3-222473 | CB: # MBS4_Others - Summary of email discussion | Lenovo - moderator |
| R3-222877 | CB: # MBS4_Others - Summary of email discussion | Lenovo - moderator |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-221699 | Mobility between MBS Supporting Nodes with TP to BL CR for TS 38.300, 38.463 | ZTE |
| R3-222024 | Discussion on remaining issues on F1-U | CATT |
| R3-222025 | Supporting lossless handover while retaining flexible MRB mapping | CATT |
| R3-222026 | (TP for TS 38.300) Lossless handover for multicast service | CATT |
| R3-222027 | [Draft] Reply LS on latest progress and outstanding issues in SA WG2 | CATT |
| R3-222063 | [TP for BL CR 38.423] on mobility between supporting nodes | Ericsson |
| R3-222082 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-222083 | (TP for TS 38.300) Mobility between MBS Supporting Nodes | Nokia, Nokia Shanghai Bell |
| R3-222084 | (TP for TS 38.300) Decision for Data Forwarding between two MBS Supporting Nodes | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, Lenovo |
| R3-222167 | (TPs to TS 38.423 and TS 38.413 BL CRs) MBS context exchange during mobility between MBS supporting nodes | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Qualcomm Incorporated, CBN, China Unicom, China Telecom |
| R3-222168 | (TPs to TS 38.423, TS 38.413 BL CRs) Support of data forwarding between MBS supporting nodes | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Qualcomm Incorporated, CBN, China Unicom, China Telecom |
| R3-222254 | Discussion on mobility with service continuity | CMCC |
| R3-222292 | (TP to TS38.423 BL): Data forwarding for mobility between MBS supporting nodes | Samsung |
| R3-222323 | Mobility between MBS Supporting Nodes with TP to BL CR for TS 38.300, 38.463 | ZTE |
| R3-222474 | CB: # MBS5_MobilitySupport - Summary of email discussion | Huawei - moderator |
| R3-222572 | CB: # MBS5_MobilitySupport - Summary of email discussion | Huawei - moderator |
| R3-222588 | [TP for BL CR 38.423] on mobility between supporting nodes | Ericsson |
| R3-222728 | (TP for TS 38.300) Lossless handover for multicast service | CATT |
| R3-222771 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-222803 | (TP for TS 38.300) Decision for Data Forwarding between two MBS Supporting Nodes | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, Lenovo |
| R3-222808 | CB: # MBS5_MobilitySupport - Summary of email discussion | Huawei - moderator |
| R3-222809 | (TP to TS 38.423 BL CR) Mobility between MBS supporting nodes | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Qualcomm Incorporated, CBN, China Unicom, China Telecom, Samsung, ZTE |
| R3-222810 | (TP to TS 38.413 BL CR) Mobility between MBS supporting nodes | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Qualcomm Incorporated, CBN, China Unicom, China Telecom, Samsung, ZTE |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-222064 | [TP for BL CR 38.300] on mobility between non supporting nodes | Ericsson |
| R3-222085 | (TP for 38.300) Minimizing Data Loss for mobility from non-MBS supporting RAN nodes | Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Qualcomm Incorporated |
| R3-222086 | (TP for 38.300) Minimizing Data Loss for mobility to non-MBS supporting RAN nodes | Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Qualcomm Incorporated |
| R3-222111 | LS on MBS data forwarding towards non MBS-supporting nodes | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, Lenovo |
| R3-222153 | Discussion on mobility between MBS supporting nodes and non-MBS supporting nodes | ZTE Corporation |
| R3-222154 | TP for MBS mobility between MBS supporting nodes and non-MBS supporting nodes | ZTE Corporation |
| R3-222180 | Discussion on mobility between MBS supporting nodes and non-MBS supporting nodes | ZTE Corporation |
| R3-222181 | TP for MBS mobility between MBS supporting nodes and non-MBS supporting nodes | ZTE Corporation |
| R3-222255 | (TP for TS 38.300) Discussion on Mobility between non-MBS supporting node and MBS supporting node | CMCC |
| R3-222475 | CB: # MBS6_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-222645 | CB: # MBS6_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-222646 | (TP for 38.300) Minimizing Data Loss for mobility from non-MBS supporting RAN nodes | Nokia, Nokia Shanghai Bell, Huawei, Lenovo, Qualcomm Incorporated, Ericsson, Samsung |
| 22.4 | Others | |
| R3-221700 | Remaining issues about Broadcast service continuity | ZTE |
| R3-222022 | (TP for 38.423) SAI for broadcast service | CATT |
| R3-222087 | (TP for 38.300) Stage 2 for Broadcast Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-222169 | (TP to TS 38.300 BL CR) Broadcast service continuity | Huawei, CBN, China Unicom, China Telecom |
| R3-222324 | Remaining issues about Broadcast service continuity | ZTE |
| R3-222476 | CB: # MBS7_BroadcastService - Summary of email discussion | ZTE - moderator |
| R3-222504 | Reply LS on MBS Service Area Identity and start procedure for broadcast service | SA2 |
| R3-222802 | (TP for TS 38.300 BL CR) FSA ID for Broadcast Service Continuity | ZTE |
| R3-222822 | TP to 38.473 on Broadcast service continuity | ZTE |
| R3-222825 | (TP for 38.423) SAI for broadcast service | CATT |
| R3-222828 | Reply LS on the Length of MBS Service Area Identity | RAN2 |
| R3-222854 | CB: # MBS7_BroadcastService - Summary of email discussion | ZTE - moderator |
| 23.1 | General | |
| R3-221584 | Introduction of ProSe authorization information | Huawei, Nokia, Nokia Shanghai Bell |
| R3-221585 | BL CR to TS38.401 on Rel-17 sidelink relay | Samsung |
| R3-221587 | Support of 5G ProSe Authorization for NG-AP | CMCC, Nokia, Nokia Shanghai Bell |
| R3-221592 | Introduction of Sidelink Relay over Xn | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-221717 | (TP for TS 38.423) Support of 5G ProSe services for XnAP | China Telecommunication |
| R3-221911 | (TP for TS 38.423): Support for Sidelink Relay | CATT |
| R3-222264 | Updated Work planning of R17 Sidelink Relay WI | CMCC, OPPO |
| R3-222477 | CB: # SLRelay1_General - Summary of email discussion | CMCC - moderator |
| R3-222592 | Introduction of Sidelink Relay over Xn | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-222601 | Support of 5G ProSe Authorization for NG-AP | CMCC, Nokia, Nokia Shanghai Bell |
| R3-222617 | Support of 5G ProSe Authorization for NG-AP | CMCC, Nokia, Nokia Shanghai Bell |
| R3-222951 | BL CR to TS38.401 on Rel-17 sidelink relay | Samsung, ZTE |
| R3-222952 | Introduction of Sidelink Relay over Xn | Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-222953 | Introduction of ProSe authorization information | Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-222981 | BL CR to TS38.401 on Rel-17 sidelink relay | Samsung, ZTE, Nokia, Nokia Shanghai Bell |
| R3-222987 | Support of 5G ProSe Authorization for NG-AP | CMCC, Nokia, Nokia Shanghai Bell |
| R3-222988 | Introduction of Sidelink Relay over Xn | Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| 23.3 | Specification of Control Plane procedures | |
| R3-221718 | Discussion on control plane procedure issues for SL Relay | China Telecommunication |
| R3-221719 | Support remote UE local ID update | China Telecommunication |
| R3-221755 | Control Plane procedures and Adaptation layer design for U2N relays | Qualcomm Incorporated |
| R3-221835 | (TP for SLrelay BLCR for 38.473) Control Plane procedures | Huawei |
| R3-221836 | (TP for SLrelay BLCR for 38.401) Control Plane procedures | Huawei |
| R3-221837 | Addition of SL Relay | Huawei |
| R3-221856 | Control plane procedures for SL Relay | Ericsson |
| R3-221857 | (TP for SL Relay BL CR to TS 38.401) Updates on overall procedures | Ericsson |
| R3-221858 | (TP for SL Relay BL CR to TS 38.470) Support of SL Relay | Ericsson |
| R3-221902 | (TP for TS 38.473 BL CR) Discussion on control procedures for L2 U2N Relay | Nokia, Nokia Shanghai Bell |
| R3-221903 | (Stage-2 F1AP CR) support for NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-221904 | (TP for TS38.401 BL CR) Update on Rel-17 Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-221910 | (TP for TS38.401 and TS38.473) Open issues for Sidelink Relay | CATT |
| R3-221912 | (TP for TS38.413) Impacts on RAN of AN Release of Relay UE | CATT |
| R3-221915 | Further discussion on F1 signalling design for the SL relay | ZTE |
| R3-221916 | (TP for SL relay BLCR to TS 38.473) PDB of Uu/PC5 RLC channel | ZTE |
| R3-221917 | Further discussion on RRC procedures for SL relay | ZTE |
| R3-221994 | (TP to SL Relay BLCR to TS 38.473) Control plane issues on SL relay | Lenovo, Motorola Mobility |
| R3-222265 | Discussion on CP issue for SL relay | CMCC |
| R3-222266 | (TP for SL relay BLCR to 38.401) Control plane | CMCC |
| R3-222320 | (TP to BL CR on TS38.401 and TS38.473) Discussion on open issues for sidelink relay | Samsung |
| R3-222478 | CB: # SLRelay2_ControlPlane - Summary of email discussion | Samsung - moderator |
| R3-222600 | CB: # SLRelay2_ControlPlane - Summary of email discussion | Samsung - moderator |
| R3-222602 | (TP for SLrelay BLCR for 38.473) Control Plane procedures | Huawei |
| R3-222603 | (Stage-2 F1AP CR) support for NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-222604 | (TP to BL CR on TS38.401) Service continuity for sidelink relay | Samsung |
| R3-222605 | (TP to BL CR on TS38.401) RRC procedures for SL relay | ZTE |
| R3-222606 | (TP for TS38.413) Impacts on RAN of AN Release of Relay UE | CATT |
| R3-222618 | Reply LS to RAN3 on mapping configuration of sidelink relay | RAN2 |
| R3-222864 | (TP for SLrelay BLCR for 38.473) Control Plane procedures | Huawei, Samsung, CMCC |
| 24.1 | General | |
| R3-221528 | CG-SDT BLCR to TS 38.473 | Samsung |
| R3-221562 | RA-SDT BLCR to TS 38.300 | ZTE |
| R3-221563 | RA-SDT BLCR to TS 38.401 | Intel Corporation |
| R3-221564 | RA-SDT BLCR to TS 38.423 | Ericsson |
| R3-221565 | Support of RACH based SDT | Nokia, Nokia Shanghai Bell |
| R3-221589 | RA-SDT BLCR to TS 38.420 | Qualcomm Incorporated |
| R3-221649 | RA-SDT BLCR to TS 38.463 | China Telecom |
| R3-221650 | CG-SDT BLCR to TS 38.470 | Lenovo, Motorola Mobility |
| R3-221651 | CG-SDT BLCR to TS 38.401 | Huawei |
| R3-222479 | CB: # SDT1_BLCRs - Summary of email discussion | Huawei - moderator |
| R3-222496 | CG-SDT BLCR to TS 38.470 | Lenovo, Motorola Mobility |
| R3-222591 | RA-SDT BLCR to TS 38.300 | ZTE |
| R3-222955 | RA-SDT BLCR to TS 38.300 | ZTE, Nokia, Nokia Shanghai Bell, China Telecommunication, Ericsson, CATT, Intel Corporation |
| R3-222956 | RA-SDT BLCR to TS 38.401 | Intel Corporation, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-222957 | RA-SDT BLCR to TS 38.420 | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation |
| R3-222958 | RA-SDT BLCR to TS 38.423 | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, NEC, CATT, Samsung |
| R3-222959 | RA-SDT BLCR to TS 38.463 | China Telecom, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE, CATT, Samsung |
| R3-222960 | Support of RACH based SDT | Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation, Samsung, CATT |
| R3-222961 | CG-SDT BLCR to TS 38.401 | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation, CATT |
| R3-222962 | CG-SDT BLCR to TS 38.470 | Lenovo, Motorola Mobility, ZTE, Nokia, Nokia Shanghai Bell |
| R3-222963 | CG-SDT BLCR to TS 38.473 | Samsung, ZTE, Nokia, Nokia Shanghai Bell, Intel Corporation, CATT |
| R3-222986 | RA-SDT BLCR to TS 38.463 | China Telecom, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE, CATT, Samsung |
| 24.2 | Support of Context Fetch and Data Forwarding | |
| R3-221775 | RACH based SDT discussion | NEC |
| R3-221776 | (TP for XNAP BL CR on RA-SDT) RACH based SDT | NEC |
| R3-221816 | (TP for TS 38.423) Conclusions on RACH-based SDT | Nokia, Nokia Shanghai Bell |
| R3-221817 | (TP for TS 38.473) Conclusions on RACH-based SDT | Nokia, Nokia Shanghai Bell |
| R3-221853 | (TP for RA-SDT BL CR to TS 38.423) Procedures for context fetch | Ericsson, ZTE, Lenovo, Motorola Mobility |
| R3-221896 | (TP for SDT BL CRs) On RA-based SDT | CATT |
| R3-221937 | (TP for RA-SDT BLCR to TS 38.300) Left issues for RA-SDT without anchor relocation case | ZTE, Ericsson |
| R3-221938 | (TP for RA-SDT BLCR to TS 38.300) Left issues for RA-SDT with anchor relocation case | ZTE |
| R3-221995 | Remaining Issues on RA-SDT | Lenovo, Motorola Mobility |
| R3-222124 | (TP to RA-SDT BL CR on TS38.473) Discussion on the remaining issues of RA-SDT | Samsung |
| R3-222170 | (TPs to RA-SDT BL CRs of TS 38.300, 38.420, 38.470) RACH based SDT without anchor relocation | Huawei |
| R3-222171 | (TP to RA-SDT BL CR of TS 38.423) RACH based SDT without anchor relocation | Huawei |
| R3-222238 | (TP for RA-SDT BL CR to TS 38.423) Support of RA-SDT | LG Electronics |
| R3-222351 | (TP for RA-SDT BL CR for TS 38.423/463) Toward the completion of RA-SDT | Intel Corporation |
| R3-222352 | (TP for RA-SDT BL CR for TS 38.423) Why relocation preference is necessary for RA-SDT as assistance info from the receiving gNB | Intel Corporation |
| R3-222353 | (TP for RA-SDT BL CR for TS 38.300/401) | Intel Corporation |
| R3-222480 | CB: # SDT2_RACHbased - Summary of email discussion | Ericsson - moderator |
| R3-222644 | CB: # SDT2_RACHbased - Summary of email discussion | Ericsson - moderator |
| R3-222773 | (TP for RA-SDT BLCR to TS 38.300) Left issues for RA-SDT without anchor relocation case | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Samsung |
| R3-222774 | (TP for RA-SDT BL CR for TS 38.401) | Intel Corporation, LG Electronics, ZTE, CATT, Ericsson, NEC, Samsung |
| R3-222775 | (TP for RA-SDT BL CR to TS 38.423) Procedures for context fetch | Ericsson, ZTE, Lenovo, Motorola Mobility, China Telecommunication, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, CATT, Intel Corporation |
| R3-222776 | (TP to RA-SDT BL CR on TS38.473) Discussion on the remaining issues of RA-SDT | Samsung, Ericsson, Intel Corporation, LG Electronics, CATT, Lenovo, NEC |
| R3-222777 | (TP to RA-SDT BL CR of TS 38.420) RACH based SDT without anchor relocation | Huawei, ZTE, Intel Corporation, CATT, Samsung |
| R3-222856 | CB: # SDT2_RACHbased - Summary of email discussion | Ericsson - moderator |
| R3-222863 | (TP to RA-SDT BL CR on TS38.473) Discussion on the remaining issues of RA-SDT | Samsung, Ericsson, Intel Corporation, LG Electronics, CATT, Lenovo, NEC |
| 24.3 | Support of CG based SDT | |
| R3-221794 | Discussion on left issues for CG-SDT | ZTE, China Telecom, Ericsson |
| R3-221795 | (TP for CG-SDT BLCR to TS 38.473) Left issue for CG-SDT | ZTE, China Telecom, Ericsson |
| R3-221801 | (TP for CG-SDT BL CR to TS 38.401) Procedures for F1 CG-SDT procedures | Ericsson, ZTE, China Telecom |
| R3-221818 | (TP for TS 38.401) Conclusions on CG-based SDT | Nokia, Nokia Shanghai Bell |
| R3-221819 | (TP for TS 38.473) Conclusions on CG-based SDT | Nokia, Nokia Shanghai Bell |
| R3-221897 | (TP for SDT BL CRs) On CG based SDT | CATT |
| R3-221996 | (TP to CG-SDT TS 38.473 BL CR) New Cause in the UE Context Release Request message | Lenovo, Motorola Mobility |
| R3-222050 | Discussion on remaining issues on E1 impact on SDT | China Telecom Corporation Ltd. |
| R3-222051 | TP to TS38.463 on the support of SDT in E1 interface | China Telecom Corporation Ltd. |
| R3-222172 | (TP to CG-SDT BL CR of TS 38.401) Leftover issues on CG-SDT | Huawei |
| R3-222239 | (TP for CG-SDT BL CR to TS 38.473) Support of CG-SDT in F1 | LG Electronics |
| R3-222240 | (TP for RA-SDT BL CR to TS 38.463) Support of SDT in E1 | LG Electronics |
| R3-222318 | (TP to CG-SDT BL CR of TS38.473) Discussion on CG-based small data transmission | Samsung |
| R3-222354 | (TP for CG-SDT BL CR for TS 38.401/473/470) Toward the completion of CG-SDT | Intel Corporation |
| R3-222481 | CB: # SDT3_CGbased - Summary of email discussion | ZTE - moderator |
| R3-222652 | CB: # SDT3_CGbased - Summary of email discussion | ZTE - moderator |
| R3-222682 | (TP to CG-SDT BL CR of TS 38.401) Leftover issues on CG-SDT | Huawei, Ericsson, ZTE, Samsung, Intel Corporation, CATT, LG Electronics, Lenovo |
| R3-222683 | (TP for CG-SDT BL CR for TS 38.473) Toward the completion of CG-SDT | Intel Corporation |
| R3-222684 | TP for CG-SDT BLCR to TS 38.470 | Lenovo, Intel Corporation, ZTE, Ericsson, LG Electronics, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| 24.4 | Others | |
| R3-221667 | LS on RAN3 impacts for non-SDT handling | RAN2 |
| R3-221668 | LS on Security for Small Data Transmission | RAN2 |
| R3-221796 | Discussion on non-SDT handling during ongoing SDT procedure | ZTE |
| R3-221854 | Handling of non-SDT arrival during SDT procedure | Ericsson |
| R3-221855 | [DRAFT] Reply LS on RAN3 impacts for non-SDT handling | Ericsson |
| R3-221898 | (TP for RA-SDT BL CR 38.463) On Continue ROHC and non-SDT | CATT |
| R3-221899 | Draft Reply LS on RAN3 impacts for non-SDT handling | CATT |
| R3-221997 | Discussion on RAN3 impacts for UL non-SDT handling | Lenovo, Motorola Mobility |
| R3-221998 | (TP to RA-SDT TS 38.463 BL CR) Non SDT Data Arrival | Lenovo, Motorola Mobility |
| R3-222032 | (TP to RA-SDT BLCR for TS38.463) Changes to Bearer Context Setup procedure | Google Inc. |
| R3-222041 | Discussion on RAN2 LS on non-SDT Handling | Qualcomm Incorporated |
| R3-222042 | [DRAFT] Reply LS on RAN3 impacts for non-SDT handling | Qualcomm Incorporated |
| R3-222173 | Considerations on CCCH solution for UL non-SDT arrival | Huawei, InterDigital |
| R3-222241 | Discussion on CCCH solution for non-SDT data | LG Electronics |
| R3-222319 | (TP to RA-SDT BL CR TS38.463) Discussion on remaining issues on SDT | Samsung |
| R3-222355 | Discussion on RAN3 impacts for non-SDT handling from RAN2 | Intel Corporation |
| R3-222356 | [Draft] Reply LS on RAN3 impacts for non-SDT handling | Intel Corporation |
| R3-222482 | CB: # SDT4_Others - Summary of email discussion | Intel - moderator |
| R3-222484 | Reply LS on Security of Small data transmission | SA3 |
| R3-222654 | CB: # SDT4_Others - Summary of email discussion | Intel - moderator |
| R3-222846 | (TP for RA-SDT BL CR for TS 38.463) | Intel Corporation, Nokia, Nokia Shanghai Bell, CATT, China Telecom, ZTE, LG Electronics, Samsung, Ericsson, Lenovo |
| 30.1 | NB-IoT and eMTC support for NTN | |
| R3-221597 | NB-IoT/eMTC support for Non-Terrestrial Networks | ZTE, CATT, Samsung, MediaTek, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated |
| R3-221599 | (BL CR for 36.423) IoT over NTN | CATT, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-221600 | Support of NTN RAT identification and NTN RAT restrictions | Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-221601 | NNSF for IoT NTN providing access over multiple countries | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-221652 | Reply LS on EPS support for IoT NTN in Rel-17 | CT1 |
| R3-221653 | Reply LS on EPS support for IoT NTN in Rel-17 | CT1 |
| R3-221655 | LS on UE providing Location Information for NB-IoT | RAN2 |
| R3-221656 | LS on security concerns for UE providing Location Information for NB-IoT | RAN2 |
| R3-221701 | Updated Work Plan on NB-IoT and eMTC Support for NTN | ZTE |
| R3-221798 | UE Location Information and IoT NTN | Ericsson LM |
| R3-221799 | [DRAFT] Reply LS on UE providing Location Information for NB-IoT | Ericsson LM |
| R3-221905 | (TP for TS36.300 BL CR) Discussion on the mapped cell ID and TAC reporting in S1AP | Nokia, Nokia Shanghai Bell |
| R3-221906 | (TP for TS36.413 BL CR) Update for the mapped cell ID and TAC reporting in S1AP | Nokia, Nokia Shanghai Bell |
| R3-221923 | Dicussion about location report and mapping in NTN-IoT | Huawei |
| R3-221924 | TP to stage 2 BL CR | Huawei, China Unicom, CMCC |
| R3-221925 | [DRAFT] Relpy LS on UE providing location information for NB-IoT | Huawei |
| R3-221962 | (TP for IoT NTN BL CRs) Cause Value and for Cross-country Scenario | CATT |
| R3-221963 | (TP for IoT NTN BL CRs) TAC Reporting in UL | CATT |
| R3-222043 | Further Discussion on NB-IoT and eMTC Support for NTN | ZTE |
| R3-222044 | (TP for IoT NTN BL CR 36.300, 36.410 and 36.413) NB-IoT and eMTC Support for NTN | ZTE |
| R3-222375 | (TP for IoT NTN BL CRs) Cause Value and for Cross-country Scenario | CATT |
| R3-222376 | (TP for IoT NTN BL CRs) TAC Reporting in UL | CATT |
| R3-222410 | CB: # 18_IoToverNTN - Summary of email discussion | ZTE - moderator |
| R3-222564 | TP to stage 2 BL CR | Huawei, China Unicom, CMCC |
| R3-222565 | CB: # 18_IoToverNTN - Summary of email discussion | ZTE - moderator |
| R3-222689 | LS Response to LS on UE providing Location Information for NB-IoT | SA2 |
| R3-222757 | [DRAFT] Reply LS on UE providing Location Information for NB-IoT | Ericsson LM |
| R3-222786 | (TP for IoT NTN BL CR 36.300) Stage 2 Clarification on IoT NTN | ZTE, Nokia, Nokia Shanghai Bell |
| R3-222787 | (TP for IoT NTN BL CR 36.410) Clean-up on NNSF | ZTE |
| R3-222791 | (TP for IoT NTN BL CR 36.413) NB-IoT and eMTC Support for NTN | ZTE |
| R3-222797 | (TP for TS36.413 BL CR) Update for the mapped cell ID and TAC reporting in S1AP | Nokia, Nokia Shanghai Bell |
| R3-222827 | (TP for IoT NTN BL CR 36.413) Cause Value for Country-specific Routing | CATT |
| R3-222831 | Reply LS on UE providing Location Information for NB-IoT | CT1 |
| R3-222858 | Reply LS on UE providing Location Information for NB-IoT | Ericsson LM |
| R3-222871 | Reply LS on opens issues for NB-IoT and eMTC support for NTN | SA3 |
| R3-222872 | Reply LS on security concerns for UE providing Location Information for NB-IoT | SA3 |
| R3-222900 | NB-IoT/eMTC support for Non-Terrestrial Networks | ZTE, CATT, Samsung, MediaTek, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated |
| R3-222901 | NNSF for IoT NTN providing access over multiple countries | Qualcomm Incorporated, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-222902 | Support of NTN RAT identification and NTN RAT restrictions | Ericsson, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| 30.2 | Multi-SIM | |
| R3-221573 | Introduction of MultiSIM support over S1 | ZTE, vivo, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Radisys, Reliance JIO |
| R3-221574 | Introduction of MultiSIM support over NG | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE, Huawei, vivo, Radisys, Reliance JIO |
| R3-221575 | Introduction of MultiSIM support over Xn | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Huawei, vivo, Radisys, Reliance JIO |
| R3-221576 | Introduction of MultiSIM support over F1 | Huawei, vivo, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO |
| R3-221577 | Introduction of MultiSIM support over E1 | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, vivo, Radisys, Reliance JIO |
| R3-221792 | (TP for BLCR Introduction of MultiSIM support over S1) Support of Multi-SIM | ZTE |
| R3-221793 | (TP for BLCR Introduction of MultiSIM support over NG/Xn/F1) Support of Multi-SIM | ZTE |
| R3-221820 | (TP for TS 38.413) Conclusions on Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-221821 | (TP for TS 38.473) Conclusions on Multi-USIM devices | Nokia, NOkia Shanghai Bell |
| R3-221926 | Discussion on MUSIM leftover issues | Huawei |
| R3-221927 | (TP to BL CR 38.473) MUSIM gap configuration | Huawei |
| R3-221930 | Introduction of Multi-USIM Support for TS 38.300 | RadiSys, Reliance JIO, Ericsson |
| R3-222035 | TP on Introduction of MultiSIM support over Xn | Ericsson |
| R3-222036 | MUSIM reaming issues | Ericsson |
| R3-222117 | (TP for LTE_NR_MUSIM CR for TS 38.413) Discussion on open issues for MUSIM UE | Samsung |
| R3-222118 | (TP for LTE_NR_MUSIM CR for TS 38.473) Discussion on supporting MUSIM gap configuration | Samsung |
| R3-222215 | Discussion on Multi-SIM | CATT |
| R3-222216 | (TP to BLCR for TS 38.463) Multi-SIM | CATT |
| R3-222249 | Discussion on MUSIM Paging Cause Support Indication | RadiSys, Reliance JIO |
| R3-222411 | CB: # 19_MultiSIM - Summary of email discussion | Ericsson - moderator |
| R3-222510 | Reply LS on alternative IMSI for MUSIM | SA2 |
| R3-222566 | CB: # 19_MultiSIM - Summary of email discussion | Ericsson - moderator |
| R3-222664 | Introduction of MultiSIM support over NG | Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE, Huawei, vivo, Radisys, Reliance JIO, CATT |
| R3-222699 | Introduction of MultiSIM support over S1 | ZTE, vivo, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Radisys, Reliance JIO, CATT |
| R3-222705 | Introduction of MultiSIM support over Xn | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Huawei, vivo, Radisys, Reliance JIO |
| R3-222706 | Introduction of MultiSIM support over F1 | Huawei, vivo, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO |
| R3-222707 | Introduction of Multi-USIM Support for TS 38.300 | RadiSys, Reliance JIO, Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE |
| R3-222739 | LS reply on RAN2 agreements for paging with service indication | SA2 |
| R3-222841 | CB: # 19_MultiSIM - Summary of email discussion | Ericsson - moderator |
| R3-222897 | Introduction of MultiSIM support over F1 | Huawei, vivo, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Radisys, Reliance JIO |
| 30.3 | UE Power Saving Enhancements | |
| R3-221578 | Support of UE Power Saving Enhancements | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated |
| R3-221582 | Addition of PEIPS Assistance Information | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT |
| R3-221583 | CR to TS38.473 for UE paging subgroup | ZTE, MediaTek, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, Qualcomm Incorporated, CATT |
| R3-221593 | Supporting UE Power Saving Enhancements | Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Ericsson, Qualcomm Incorporated, CATT |
| R3-221594 | (BL CR to TS 38.410) Support for ePowerSaving | CATT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Incorporated, Samsung |
| R3-221596 | (BL CR to TS 38.470) Support for UE Power Saving Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson, ZTE |
| R3-221745 | (TP for XnAP BL CR on UE Power Savings) EN Removal on RAN Paging | Qualcomm Incorporated |
| R3-221822 | (TP for TS 38.470 & TS 38.300) Stage 2 conclusions for UE Power Saving Enhancements | Nokia, Nokia Shanghai Bell |
| R3-221823 | (TP for TS 38.473) Stage 3 conclusions for UE Power Saving Enhancements | Nokia, Nokia Shanghai Bell |
| R3-221971 | (TP for Powersaving BLCR for TS 38.423) Supporting UE Power Saving Enhancements | Huawei |
| R3-221972 | (TP for Powersaving BLCR for TS 38.473 and TS 38.413) Supporting UE Power Saving Enhancements | Huawei |
| R3-222196 | Work plan for UE power saving enhancements WI | ZTE,MediaTek Inc. |
| R3-222201 | (TP for TS 38.413) Support for UE power saving | CATT |
| R3-222250 | Left issues on UE power saving enhancement | ZTE Corporation, MediaTek Inc. |
| R3-222251 | (TP to TS38.473 and TS38.423) paging subgroup | ZTE Corporation, MediaTek Inc. |
| R3-222316 | (TP to BL CR on TS38.473) Further discussion on UE power saving | Samsung |
| R3-222412 | CB: # 20_UEPowerSaving - Summary of email discussion | ZTE - moderator |
| R3-222522 | TP to TS 38.300 BL CR: Addition of PEIPS over Xn | Ericsson |
| R3-222548 | CR to TS38.473 for UE paging subgroup | ZTE, MediaTek, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, Qualcomm Incorporated, CATT |
| R3-222549 | Supporting UE Power Saving Enhancements | Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Ericsson, Qualcomm Incorporated, CATT |
| R3-222567 | CB: # 20_UEPowerSaving - Summary of email discussion | ZTE - moderator |
| R3-222681 | (TP for Powersaving BLCR for TS 38.470) Introduction of SIBx on TRS resources | Huawei |
| R3-222772 | (TP to BL CR on TS38.473) Further discussion on UE power saving | Samsung |
| R3-222848 | Reply LS on paging subgrouping and PEI | ZTE |
| R3-222849 | (TP to TS38.423) paging subgroup | ZTE Corporation, MediaTek Inc., Qualcomm Incorporated, Huawei |
| R3-222850 | (TP for TS 38.413) Support for UE power saving | CATT, ZTE |
| R3-222874 | Reply LS on paging subgrouping and PEI | ZTE |
| R3-222964 | Addition of PEIPS Assistance Information | Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, CATT |
| R3-222965 | Support of UE Power Saving Enhancements | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated, ZTE, Huawei |
| R3-222966 | Supporting UE Power Saving Enhancements | Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Ericsson, Qualcomm Incorporated, CATT |
| R3-222967 | (BL CR to TS 38.470) Support for UE Power Saving Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson, ZTE |
| R3-222968 | CR to TS38.473 for UE paging subgroup | ZTE, MediaTek, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, Qualcomm Incorporated, CATT |
| 30.4 | UPIP Support with EN-DC | |
| R3-221606 | Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP | ZTE, China Telecom, Ericsson, Vodafone, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei |
| R3-221607 | Introduction of User Plane Integrity Protection in EPS | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Vodafone, Ericsson |
| R3-221608 | Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Vodafone, Ericsson |
| R3-221741 | (TP for S1AP BL CR on UP IP) Remaining functionality support for IP UP in EPS | Qualcomm Incorporated |
| R3-221824 | (TP for TS 36.423) Support of EPS User Plane Integrity Protection | Nokia, Nokia Shanghai Bell |
| R3-221973 | (TP for UPIP BLCR for TS 36.423) Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT |
| R3-221974 | (TP for UPIP BLCR for TS 36.413) Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT |
| R3-221975 | (TP for UPIP BLCR for TS 38.463) Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT |
| R3-222040 | Further discussion on UPIP EPC | Ericsson |
| R3-222197 | (TPs for TS38.401 TS36.413 TS36.423) Supporting UPIP | ZTE |
| R3-222347 | EPS User Plane Integrity Protection with non-supporting nodes | VODAFONE |
| R3-222413 | CB: # 21_EPSUPIP - Summary of email discussion | Vodafone - moderator |
| R3-222485 | Reply LS on LTE User Plane Integrity Protection | SA2 |
| R3-222523 | Reply LS on LTE User Plane Integrity Protection | SA3 |
| R3-222568 | Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP | ZTE, China Telecom, Ericsson, Vodafone, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei |
| R3-222569 | Introduction of User Plane Integrity Protection in EPS | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Vodafone, Ericsson |
| R3-222570 | Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Vodafone, Ericsson, Intel Corporation |
| R3-222571 | CB: # 21_EPSUPIP - Summary of email discussion | Vodafone - moderator |
| R3-222700 | (TP for UPIP BLCR for TS 36.423) Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT |
| R3-222730 | (TP for S1AP BL CR on UP IP) Remaining functionality support for IP UP in EPS | Qualcomm Incorporated |
| R3-222769 | (TP for E1AP BL CR on UP IP) Support for UPIP in EPS | ZTE |
| R3-222818 | CB: # 21_EPSUPIP - Summary of email discussion | Vodafone - moderator |
| R3-222899 | (TP for UPIP BLCR for TS 36.423) Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT |
| R3-222970 | Introduction of User Plane Integrity Protection in EPS | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Vodafone, Ericsson |
| R3-222971 | Supporting EPS User Plane Integrity Protection | Huawei, Orange, CATT, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Vodafone, Ericsson, Intel Corporation |
| R3-222972 | Support for User Plane Integrity Protection support for EPC connected architectures with EN-DC capable UE_E1AP | ZTE, China Telecom, Ericsson, Vodafone, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation |
| R3-222982 | Introduction of User Plane Integrity Protection in EPS | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Vodafone, Ericsson, Intel Corporation |
| 30.5 | Others | |
| R3-221514 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson |
| R3-221536 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221586 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-221644 | Draft TS 37.482 v0.3.0 | Huawei |
| R3-221645 | Draft TS 37.483 v0.1.0 | Ericsson |
| R3-221646 | Draft TS 37.480 v0.1.0 | Nokia, Nokia Shanghai Bell |
| R3-221647 | Draft TS 37.481 v0.1.0 | Intel Corporation |
| R3-221928 | Correction on enhanced eNB architecture evolution | Huawei |
| R3-222232 | Rapporteur Editorial corrections to 37.482 | Huawei |
| R3-222414 | CB: # 22_eNBarchEvo - Summary of email discussion | Huawei - moderator |
| R3-222519 | Rapporteur Editorial corrections to 37.482 | Huawei |
| R3-222574 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222575 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson |
| R3-222576 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-222577 | Draft TS 37.482 v0.3.1 | Huawei |
| R3-222578 | Draft TS 37.483 v0.1.1 | Ericsson |
| R3-222579 | Draft TS 37.480 v0.1.1 | Nokia, Nokia Shanghai Bell |
| R3-222580 | Draft TS 37.481 v0.1.1 | Intel Corporation |
| R3-222710 | Correction on enhanced eNB architecture evolution | Huawei |
| R3-222711 | CB: # 22_eNBarchEvo - Summary of email discussion | Huawei - moderator |
| R3-222973 | Draft TS 37.480 v0.2.0 | Nokia, Nokia Shanghai Bell |
| R3-222974 | Draft TS 37.482 v0.4.0 | Huawei |
| R3-222983 | draft TS37.480 v1.1.0 | Nokia, Nokia Shanghai Bell |
| R3-222984 | draft TS37.482 v1.1.0 | Huawei |
| R3-222985 | draft TS37.483 v1.1.0 | Ericsson |
| 31.1.1 | Inclusive Language Review | |
| R3-221640 | Inclusive language review | Huawei |
| R3-221641 | Inclusive language review | Huawei |
| R3-221642 | Inclusive language cleanup for TS25.484 | ZTE |
| R3-221643 | Inclusive language review for TS 25.467 | Nokia, Nokia Shanghai Bell |
| R3-221688 | Inclusive Language Review Status and Upcoming Steps | Ericsson (coordinator) |
| R3-221694 | Inclusive language review for TS 36.413 | Nokia, Nokia Shanghai Bell |
| R3-221708 | Inclusive language review for TS 25.402 | Nokia, Nokia Shanghai Bell |
| R3-222399 | CB: # 10_Inclusive_Language - Summary of email discussion | Ericsson - moderator |
| R3-222667 | Inclusive language review for TS 36.413 | Nokia, Nokia Shanghai Bell |
| 31.1.2 | Rapporteur Review | |
| R3-221709 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-221825 | Rapporteur Corrections of TS 38.415 | Nokia, Nokia Shanghai Bell |
| R3-221826 | Rapporteur Corrections of TS 38.410 | Nokia, Nokia Shanghai Bell |
| R3-221828 | NRPPa Rapporteur Corrections | Ericsson-LG Co., LTD |
| R3-221838 | Editorial corrections | Huawei |
| R3-221839 | Editorial corrections | Huawei |
| R3-221859 | X2AP Rapporteur Corrections | Ericsson (rapporteur) |
| R3-221907 | S1AP Rapporteur Corrections | Nokia, Nokia Shanghai Bell |
| R3-222052 | X2AP Rapporteur Corrections | Ericsson (Rapporteur) |
| R3-222057 | XnAP Rapporteur Corrections | Ericsson |
| R3-222115 | E1AP Rapporteur Corrections | Ericsson |
| R3-222400 | CB: # 11_RapporteurUpdates - Summary of email discussion | Huawei - moderator |
| R3-222491 | Editorial corrections | Huawei |
| R3-222492 | XnAP Rapporteur Corrections | Ericsson |
| R3-222520 | Editorial corrections to 38.462 | Huawei |
| R3-222582 | Correction of maxNARFCN in ASN.1 | Samsung, Nokia, Nokia Shanghai Bell, CATT, ZTE, Ericsson, China Telecom, China Unicom, NEC |
| R3-222731 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
| 31.1.3 | Endorsed Rel-17 TEI CRs Review | |
| R3-221611 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-221612 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-221613 | Signalling of Neighbour cell CSI-RS configuration information over Xn [CSIRSXn] | Ericsson, China Telecom |
| R3-221614 | Signalling of Neighbour cell CSI-RS configuration information over X2 [CSIRSX2] | Ericsson, China Telecom |
| R3-221615 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, CATT, Samsung |
| R3-221616 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, Huawei, CATT, Samsung |
| R3-221617 | Support of Enhancement of Redundant PDU Sessions [Paired_ID] | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, CATT, Samsung |
| R3-221618 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-221619 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei |
| R3-221620 | Removal of ETWS/CMAS restriction in SNPN | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-221627 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | Ericsson, CATT, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-221628 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-221632 | CSI-RS configuration request Indicator [CSIRSXn] | Ericsson, China telecom, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-221633 | Inter MN resume without SN change [InterMNResume] | Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung, Radisys, Reliance JIO |
| R3-221634 | Addition of the Retrieve UE Context Confirm procedure [InterMNResume] | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson, China Telecom, T-Mobile USA, ZTE, Intel Corporation, Samsung |
| R3-221635 | Inter-MN RRC Resume without SN change [InterMNResume] | Ericsson, Qualcomm Incorporated, Huawei, Intel Corporation, China Telecom, T-Mobile USA, ZTE, Nokia, Nokia Shanghai Bell, Samsung, RadiSys, Reliance JIO, Google Inc. |
| R3-221636 | E1 TS 38.460 specification transfer to TS 37.480 | Nokia, Nokia Shanghai Bell |
| R3-221637 | Transfer of E1 interface specification from 38-series to 37-series | Huawei |
| R3-221638 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series | Intel Corporation |
| R3-221639 | E1AP specification transfer to TS 37.483 | Ericsson |
| R3-221862 | CSI-RS configuration request Indicator [CSIRSX2] | Ericsson, China telecom, Huawei, Nokia Shanghai Bell, ZTE |
| R3-222401 | CB: # 12_R17TEICR_Review - Summary of email discussion | Qualcomm - moderator |
| R3-222536 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | Ericsson, CATT, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-222712 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-222713 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-222716 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series | Intel Corporation |
| R3-222734 | Transfer of E1 interface specification from 38-series to 37-series | Huawei |
| R3-222747 | E1 TS 38.460 specification transfer to TS 37.480 | Nokia, Nokia Shanghai Bell |
| R3-222847 | CB: # 12_R17TEICR_Review - Summary of email discussion | Qualcomm - moderator |
| 31.2.1 | Local NG-RAN Node Identifier | |
| R3-221629 | Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive] | Ericsson, ZTE, Radisys, Reliance JIO, China Telecom, Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-221631 | Support flexible I-RNTI partitioning [RRCInactive] | ZTE, Radisys, Reliance JIO, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Huawei |
| R3-221725 | Further discussion on Local NG-RAN Node Identifier Update | Huawei |
| R3-221726 | Support flexible I-RNTI partitioning [RRCInactive] | Huawei |
| R3-221790 | Discussion the remaining issue on I-RNTI partitioning | ZTE, Radisys, Reliance JIO, China Telecom |
| R3-221791 | CR for TS 38.423 on I-RNTI partitioning[RRCInactive] | ZTE, Radisys, Reliance JIO, China Telecom |
| R3-221860 | On the use of Local NG-RAN node Identifier | Ericsson |
| R3-221861 | Support flexible I-RNTI partitioning [RRCInactive] | Ericsson |
| R3-221934 | Discussion on issues in I-RNTI Partitioning | RadiSys, Reliance JIO, ZTE |
| R3-222247 | Support flexible I-RNTI Decode | RadiSys, Reliance JIO, ZTE |
| R3-222402 | CB: # 13_LocalNG-RANnode_Identifier - Summary of email discussion | ZTE - moderator |
| R3-222525 | CB: # 13_LocalNG-RANnode_Identifier - Summary of email discussion | ZTE - moderator |
| R3-222598 | Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive] | Ericsson, ZTE, Radisys, Reliance JIO, China Telecom, Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-222599 | Support flexible I-RNTI partitioning [RRCInactive] | ZTE, Radisys, Reliance JIO, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Huawei |
| 31.2.2 | PDCP Duplication | |
| R3-221800 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-221802 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-221804 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-221806 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-221940 | correction on UL PDCP duplication[UL_duplication] | ZTE |
| R3-221957 | Assistance information for UL duplication | Huawei, China Unicom, China Telecom, CATT |
| R3-221958 | Assistance information for UL duplication [UL_duplication] | Huawei, China Unicom, China Telecom, CATT |
| R3-222217 | Discussion on UL PDCP Duplication | CATT |
| R3-222218 | CR to 38.425 for handling of UL PDCP Duplication status information[UL_duplication] | CATT |
| R3-222403 | CB: # 14_PDCPDuplication - Summary of email discussion | CATT - moderator |
| 31.2.3 | PRACH Coordination Between LTE and NR | |
| R3-221727 | PRACH Coordination Between LTE and NR | Huawei |
| R3-221728 | PRACH Coordination Between LTE and NR | Huawei |
| R3-221729 | PRACH Coordination Between LTE and NR | Huawei |
| R3-222048 | Comparison of Potential Solutions for PRACH Coordination | China Telecom, ZTE, Huawei, CATT |
| R3-222049 | [DRAFT] LS on the support of non-collocated co-channel deployment of NR and LTE | China Telecom Corporation Ltd. |
| R3-222094 | Analysis of PRACH Coordination Between LTE and NR | Ericsson |
| R3-222198 | Consideration on Resource Coordination between LTE and NR | ZTE |
| R3-222199 | TP for PRACH Coordination Between LTE and NR | ZTE |
| R3-222404 | CB: # 15_PRACHCoordination - Summary of email discussion | China Telecom - moderator |
| 31.2.4 | Support exchange of protocol support at target RAN node for NG handover | |
| R3-221738 | Further discussion on RACS Capability Detection for S1 and NG handover | Qualcomm Incorporated, Vodafone |
| R3-221739 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-221740 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-221954 | On node capability detection for non-direct-connected nodes | Huawei, China Unicom, China Telecom |
| R3-221955 | On node capability detection for non-direct-connected nodes [Node_Cap_Dect] | Huawei, China Unicom, China Telecom |
| R3-221956 | On node capability detection for non-direct-connected nodes [Node_Cap_Dect] | Huawei, China Unicom, China Telecom |
| R3-222058 | [TP for 38.413 and 36.413] On Remote Criticality | Ericsson |
| R3-222405 | CB: # 16_ProtocolSupport - Summary of email discussion | Huawei - moderator |
| R3-222493 | [TP for 38.413 and 36.413] On Remote Criticality | Ericsson |
| R3-222527 | CB: # 16_ProtocolSupport - Summary of email discussion | Huawei - moderator |
| R3-222778 | Support exchange of protocol support at target RAN node for NG handover | Ericsson |
| R3-222779 | Support exchange of protocol support at target RAN node for NG handover | Ericsson |
| R3-222852 | Detection of RACS support at target during N2/S1 handover [RACS_S1_NG] | Qualcomm Incorporated, Vodafone, Nokia, Nokia Shanghai Bell |
| R3-222853 | Detection of RACS support at target during N2/S1 handover [RACS_S1_NG] | Qualcomm Incorporated, Vodafone, Nokia, Nokia Shanghai Bell |
| R3-222898 | Detection of RACS support at target during N2/S1 handover [RACS_S1_NG] | Qualcomm Incorporated, Vodafone, Nokia, Nokia Shanghai Bell |
| 31.2.5 | CHO with SCG configuration | |
| R3-221716 | Discussion on CHO with SCG configuration | China Telecommunication |
| R3-221730 | Discussion on CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221731 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221732 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221733 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221734 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221735 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom |
| R3-221751 | CHO with SCG configuration | Qualcomm Incorporated |
| R3-221758 | CHO with SCG configuration kept at the target | Nokia, Nokia Shanghai Bell, CMCC, Vodafone |
| R3-221759 | Enabling CHO with SCG configuration [CHOwithDCkept] | Nokia, Nokia Shanghai Bell, CMCC, Vodafone |
| R3-221760 | Enabling CHO with SCG configuration [CHOwithDCkept] | Nokia, Nokia Shanghai Bell, CMCC, Vodafone |
| R3-221761 | Response LS on Conditional Handover with SCG configuration scenarios | Nokia, Nokia Shanghai Bell |
| R3-222033 | (TP to CPAC BLCR for TS36.423) Handling of SN to MN Container in CHO with SCG configuration | Google Inc. |
| R3-222034 | (TP to CPAC BLCR for TS38.423) Handling of SN to MN Container in CHO with SCG configuration | Google Inc. |
| R3-222116 | Remaining work to support CHO with SCG configuration | Ericsson |
| R3-222219 | Discussion on CHO with SCG configuration | CATT |
| R3-222220 | CR to 38.423 for CHO with SCG configuration [CHOwithSCG] | CATT |
| R3-222372 | Support CHO with SCG configuration | ZTE |
| R3-222373 | Support CHO with SCG configuration | ZTE |
| R3-222406 | CB: # 17_CHOwithSCG - Summary of email discussion | Nokia - moderator |
| R3-222821 | Support of CHO with SCG configuration | Huawei, China Telecom, China Unicom, CATT, Intel Corporation, Google Inc. |
| R3-222838 | Enabling CHO with SCG configuration [CHOwithDCkept] | Nokia, Nokia Shanghai Bell, CMCC, Vodafone, Intel Corporation, CATT |
| R3-222839 | Enabling CHO with SCG configuration [CHOwithDCkept] | Nokia, Nokia Shanghai Bell, CMCC, Vodafone, Intel Corporation, CATT |
| R3-222840 | Response LS on Conditional Handover with SCG configuration scenarios | Nokia, Nokia Shanghai Bell |
| 31.2.6 | Others | |
| R3-222046 | Clarification of DU Early Identification capability for MPS | Peraton Labs, CISA ECD, AT&T |
| 32 | Any other business | |
| R3-221885 | History of Measurement Amount | Huawei |
| R3-221886 | CR to 38.455 on Measurement Amount | Huawei |
| R3-221887 | CR to 38.473 on Measurement Amount | Huawei |
| R3-222095 | LS on Flexible gNB ID | Ericsson |
| R3-222096 | Discussion and way forward on Flexible gNB-ID solutions | Ericsson, Bell Mobility, Telus, Verizon Wireless, China Telecom |
| R3-222389 | Response to R3-222096 | ZTE Corporation |
| R3-222458 | Response to R3-222096 | Huawei |